CVE-2021-47426: bpf, s390: Fix potential memory leak about jit_data
In the Linux kernel, the following vulnerability has been resolved:
bpf, s390: Fix potential memory leak about jit_data
Make sure to free jit_data through kfree() in the error path.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the BPF JIT code for s390 systems. In an error path, allocated jit_data was not freed. The likely business impact is resource exhaustion or instability on affected Linux systems, but the public bundle provides no CVSS score, no confirmed exploitation, and limited impact detail.
Executive priority
Prioritize this in normal kernel patch management for any Linux s390 estate. Escalate only if critical s390 workloads run affected kernels or vendor advisories assign higher severity. Current public evidence does not support emergency treatment.
Technical view
CVE-2021-47426 fixes a potential memory leak in Linux kernel bpf/s390 JIT handling. The source says jit_data must be freed with kfree() in the error path. The affected data identifies Linux kernel versions including 5.4, 5.4.153, 5.10.73, 5.14.12, and 5.15, with stable kernel commits referenced as fixes.
Likely exposure
Exposure appears limited to Linux systems using the s390 BPF JIT code path on affected kernel versions. Organizations without IBM s390 or s390x Linux workloads are less likely to be exposed. The provided affected-version data is incomplete, so distribution-specific advisories should drive final scoping.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. No public exploit status, attack prerequisites, or exploitability details are provided. Treat this as a kernel reliability and resource-management issue until vendor advisories provide clearer severity or exploitation information.
Researcher notes
The key evidence is narrow: a kernel stable fix freeing jit_data in the bpf/s390 JIT error path. The bundle lacks CVSS, CWE, exploitability analysis, and precise distribution package mapping. Avoid broad Linux exposure claims beyond affected s390 BPF JIT code.
Mitigation direction
Apply vendor kernel updates containing the referenced stable Linux fixes.
Prioritize Linux s390 systems running affected kernel branches.
Check distribution advisories for exact fixed package versions.
Reboot systems if required for the patched kernel to run.
If patching is delayed, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux s390 or s390x systems and running kernel versions.
Confirm installed kernel packages include the referenced stable fix commits.
Verify the active kernel after reboot is the patched version.
Review vendor advisories for affected and fixed version mapping.
Monitor affected systems for unusual memory pressure until patched.
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-2021-47426 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.