{
  "threat_severity" : "Low",
  "public_date" : "2025-12-30T00:00:00Z",
  "bugzilla" : {
    "description" : "kernel: powerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT",
    "id" : "2426174",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2426174"
  },
  "cvss3" : {
    "cvss3_base_score" : "2.5",
    "cvss3_scoring_vector" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L",
    "status" : "verified"
  },
  "cwe" : "CWE-663",
  "details" : [ "In the Linux kernel, the following vulnerability has been resolved:\npowerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT\nlppaca_shared_proc() takes a pointer to the lppaca which is typically\naccessed through get_lppaca().  With DEBUG_PREEMPT enabled, this leads\nto checking if preemption is enabled, for example:\nBUG: using smp_processor_id() in preemptible [00000000] code: grep/10693\ncaller is lparcfg_data+0x408/0x19a0\nCPU: 4 PID: 10693 Comm: grep Not tainted 6.5.0-rc3 #2\nCall Trace:\ndump_stack_lvl+0x154/0x200 (unreliable)\ncheck_preemption_disabled+0x214/0x220\nlparcfg_data+0x408/0x19a0\n...\nThis isn't actually a problem however, as it does not matter which\nlppaca is accessed, the shared proc state will be the same.\nvcpudispatch_stats_procfs_init() already works around this by disabling\npreemption, but the lparcfg code does not, erroring any time\n/proc/powerpc/lparcfg is accessed with DEBUG_PREEMPT enabled.\nInstead of disabling preemption on the caller side, rework\nlppaca_shared_proc() to not take a pointer and instead directly access\nthe lppaca, bypassing any potential preemption checks.\n[mpe: Rework to avoid needing a definition in paca.h and lppaca.h]", "A debug warning issue was found in PowerPC pseries code. When DEBUG_PREEMPT is enabled, accessing lppaca_shared_proc() triggers spurious preemption warnings because it uses smp_processor_id() in preemptible context." ],
  "statement" : "This only produces warnings when CONFIG_DEBUG_PREEMPT is enabled, which is a debug configuration not used in production kernels. The warning itself is harmless as the code logic is correct regardless of which CPU's lppaca is accessed.",
  "affected_release" : [ {
    "product_name" : "Red Hat Enterprise Linux 9",
    "release_date" : "2024-11-12T00:00:00Z",
    "advisory" : "RHSA-2024:9315",
    "cpe" : "cpe:/a:redhat:enterprise_linux:9",
    "package" : "kernel-0:5.14.0-503.11.1.el9_5"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "release_date" : "2024-11-12T00:00:00Z",
    "advisory" : "RHSA-2024:9315",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9",
    "package" : "kernel-0:5.14.0-503.11.1.el9_5"
  } ],
  "package_state" : [ {
    "product_name" : "Red Hat Enterprise Linux 10",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:10"
  }, {
    "product_name" : "Red Hat Enterprise Linux 6",
    "fix_state" : "Out of support scope",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:6"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Fix deferred",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Fix deferred",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Fix deferred",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Fix deferred",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Fix deferred",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  } ],
  "references" : [ "https://www.cve.org/CVERecord?id=CVE-2023-54267\nhttps://nvd.nist.gov/vuln/detail/CVE-2023-54267\nhttps://lore.kernel.org/linux-cve-announce/2025123059-CVE-2023-54267-6736@gregkh/T" ],
  "name" : "CVE-2023-54267",
  "csaw" : false
}