LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48755: powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06

In the Linux kernel, the following vulnerability has been resolved: powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06 Johan reported the below crash with test_bpf on ppc64 e5500: test_bpf: #296 ALU_END_FROM_LE 64: 0x0123456789abcdef -> 0x67452301 jited:1 Oops: Exception in kernel mode, sig: 4 [#1] BE PAGE_SIZE=4K SMP NR_CPUS=24 QEMU e500 Modules linked in: test_bpf(+) CPU: 0 PID: 76 Comm: insmod Not tainted 5.14.0-03771-g98c2059e008a-dirty #1 NIP: 8000000000061c3c LR: 80000000006dea64 CTR: 8000000000061c18 REGS: c0000000032d3420 TRAP: 0700 Not tainted (5.14.0-03771-g98c2059e008a-dirty) MSR: 0000000080089000 <EE,ME> CR: 88002822 XER: 20000000 IRQMASK: 0 <...> NIP [8000000000061c3c] 0x8000000000061c3c LR [80000000006dea64] .__run_one+0x104/0x17c [test_bpf] Call Trace: .__run_one+0x60/0x17c [test_bpf] (unreliable) .test_bpf_init+0x6a8/0xdc8 [test_bpf] .do_one_initcall+0x6c/0x28c .do_init_module+0x68/0x28c .load_module+0x2460/0x2abc .__do_sys_init_module+0x120/0x18c .system_call_exception+0x110/0x1b8 system_call_common+0xf0/0x210 --- interrupt: c00 at 0x101d0acc <...> ---[ end trace 47b2bf19090bb3d0 ]--- Illegal instruction The illegal instruction turned out to be 'ldbrx' emitted for BPF_FROM_[L|B]E, which was only introduced in ISA v2.06. Guard use of the same and implement an alternative approach for older processors.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE affects Linux on some powerpc64 systems. The kernel BPF JIT could generate an instruction that older processors do not support, causing an illegal-instruction crash. The business risk is concentrated in niche PPC64 estates, not general Linux fleets.

Executive priority

Low for most organizations; moderate only for operators with legacy PPC64 Linux infrastructure where kernel crashes affect availability-sensitive services.

Technical view

The powerpc64 BPF JIT emitted `ldbrx` for BPF endian-conversion paths, but `ldbrx` requires Power ISA v2.06. On older processors such as ppc64 e5500, this could trigger a kernel-mode illegal instruction. The upstream fix limits `ldbrx` use and adds an alternate path for older processors.

Likely exposure

Exposure appears limited to Linux powerpc64 deployments using affected kernels on processors below Power ISA v2.06, especially where BPF JIT paths are exercised. x86, ARM, and newer compliant Power processors are not indicated by the provided sources.

Exploitation context

No active exploitation is cited. The bundle marks KEV as false and provides no exploit reports. The evidence describes a crash found during `test_bpf`, so treat this primarily as stability and availability risk unless vendor guidance says otherwise.

Researcher notes

The provided evidence is narrow but clear: an instruction-selection bug in the powerpc64 BPF JIT. No CVSS, CWE, exploit status, or broad impact statement is supplied. Downstream kernel package status must be verified with the relevant Linux distribution.

Mitigation direction

  • Update affected PPC64 kernels to builds containing the referenced stable fixes.
  • Prioritize older Power ISA systems, including e5500-class hardware.
  • Use vendor or distribution advisories to confirm backported fixed kernel versions.
  • If updates are unavailable, seek vendor guidance before relying on workarounds.

Validation and detection

  • Inventory Linux powerpc64 systems and processor ISA compatibility.
  • Check running kernel versions against vendor fixed packages or stable commits.
  • Confirm BPF JIT exposure on affected PPC64 hosts.
  • Review crash logs for kernel illegal-instruction events in BPF paths.
Prepared
Confidence
medium
Sources
6

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-48755 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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux156d0e290e969caba25f1851c52417c14d141b24, 156d0e290e969caba25f1851c52417c14d141b24, 156d0e290e969caba25f1851c52417c14d141b24, 156d0e290e969caba25f1851c52417c14d141b24unaffected
LinuxLinux4.8, 0, 5.10.96, 5.15.19, 5.16.5, 5.17affected
Weakness

CWE details

No CWE listed

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