CVE-2022-48770: bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
In the Linux kernel, the following vulnerability has been resolved:
bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
task_pt_regs() can return NULL on powerpc for kernel threads. This is
then used in __bpf_get_stack() to check for user mode, resulting in a
kernel oops. Guard against this by checking return value of
task_pt_regs() before trying to obtain the call chain.
Security readout for executives and security teams
Plain-English summary
This Linux kernel bug can crash the kernel when BPF stack collection touches missing register state on powerpc kernel threads. The source describes a kernel oops, so the business risk is availability disruption, not confirmed data theft or privilege escalation.
Executive priority
Treat as a targeted availability risk for relevant Linux fleets, especially powerpc systems. Prioritize patch confirmation over emergency response unless internal evidence shows crashes or vendor advisories rate it higher.
Technical view
bpf_get_task_stack() can reach __bpf_get_stack() with task_pt_regs() returning NULL on powerpc kernel threads. The missing NULL check can lead to dereferencing absent pt_regs while checking user mode, causing a kernel oops. Stable kernel commits add a guard before obtaining the call chain.
Likely exposure
Exposure appears limited to Linux systems running affected kernels where powerpc kernel-thread stack collection through BPF paths is reachable. The bundle does not identify affected distributions, appliances, cloud images, or package names.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The available evidence supports a crash/oops condition, but does not describe public exploitation, remote reachability, or weaponized procedures.
Researcher notes
The source evidence is narrow: a NULL pt_regs path on powerpc kernel threads during BPF stack collection. There is no CVSS, CWE, exploit report, or distribution matrix in the bundle, so exposure assessment should rely on kernel provenance and vendor backports.
Mitigation direction
Apply Linux stable kernel updates containing the referenced fixes.
Check distribution vendor advisories for backported kernel packages.
Prioritize powerpc Linux systems using BPF tracing or observability.
Schedule maintenance where kernel replacement requires reboot.
Do not assume non-powerpc impact without vendor confirmation.
Validation and detection
Inventory Linux kernel versions and CPU architectures.
Confirm installed kernels include a referenced stable fix or vendor backport.
Review kernel logs for oops events involving BPF stack collection.
Test BPF tracing workflows after kernel update.
Track distro advisory status for each deployed kernel stream.
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-48770 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.