LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50012: powerpc/64: Init jump labels before parse_early_param()

In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is again subroutine of early_init_devtree(). For example booting with "threadirqs": static_key_enable_cpuslocked(): static key '0xc000000002953260' used before call to jump_label_init() WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120 ... NIP static_key_enable_cpuslocked+0xfc/0x120 LR static_key_enable_cpuslocked+0xf8/0x120 Call Trace: static_key_enable_cpuslocked+0xf8/0x120 (unreliable) static_key_enable+0x30/0x50 setup_forced_irqthreads+0x28/0x40 do_early_param+0xa0/0x108 parse_args+0x290/0x4e0 parse_early_options+0x48/0x5c parse_early_param+0x58/0x84 early_init_devtree+0xd4/0x518 early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50012 is a Linux kernel initialization-order flaw on 64-bit PowerPC. Certain early boot handling, such as the cited threadirqs example, can use static keys before jump labels are initialized. The source shows a kernel warning during boot, but does not establish broader security impact.

Executive priority

Treat as low immediate business urgency unless you operate 64-bit PowerPC Linux systems. Because severity and exploitability are not defined, prioritize inventory and routine kernel patch management over emergency response.

Technical view

In powerpc/64 early boot, jump_label_init() was called too late from setup_feature_keys(). parse_early_param(), reached through early_init_devtree(), may enable static keys first. The upstream fix calls jump_label_init() immediately before parse_early_param() in early_init_devtree().

Likely exposure

Exposure appears limited to Linux kernel deployments on 64-bit PowerPC using affected kernel builds. The bundle lists upstream Linux versions and stable commits, but distro-specific package status must be checked with vendor advisories.

Exploitation context

No active exploitation is cited, and KEV is false. The evidence describes a boot-time warning caused by an initialization ordering bug. The bundle does not document remote exploitation, local privilege escalation, or a weaponized exploit path.

Researcher notes

The available evidence is narrow: initialization ordering, a threadirqs-triggered warning example, and upstream stable commits. There is no CVSS, CWE, or documented exploitability. Avoid extrapolating impact beyond affected powerpc/64 kernel boot behavior.

Mitigation direction

  • Identify any 64-bit PowerPC Linux systems in the environment.
  • Check distro advisories for CVE-2022-50012 kernel package status.
  • Update affected kernels using vendor-supported packages when available.
  • If no vendor fix is listed, track the referenced upstream stable commits.

Validation and detection

  • Confirm whether systems run 64-bit PowerPC Linux kernels.
  • Compare deployed kernel versions with vendor advisories and the CVE record.
  • Review boot logs for static key or jump_label_init warnings.
  • Verify the relevant stable fix is present in patched kernel builds.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50012 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux91cc470e797828d779cd4c1efbe8519bcb358bae, 91cc470e797828d779cd4c1efbe8519bcb358bae, 91cc470e797828d779cd4c1efbe8519bcb358baeunaffected
LinuxLinux5.15, 0, 5.15.63, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.