PatchSiren cyber security CVE debrief
CVE-2026-93112 Linux CVE debrief
A vulnerability in the Linux kernel has been resolved, requiring a BPF cpumask for bpf_cpumask_populate() to prevent the verifier from accepting borrowed cpumask pointers as writable destinations. The Linux kernel vulnerability requires attention from developers and administrators to assess exposure and prioritize verification of affected systems. The vulnerability has been resolved, but scope of affected systems and versions requires clarification. Verification of BPF cpumask usage in kernel code is necessary.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Linux kernel developers, administrators, and users who rely on Linux kernel-based systems. Linux kernel developers and administrators should assess exposure and prioritize verification of affected systems. The vulnerability requires attention from developers and administrators to assess exposure and prioritize verification of affected systems.
Why it matters
The Linux kernel vulnerability requires attention from developers and administrators to assess exposure and prioritize verification of affected systems.
- Verification of BPF cpumask usage in kernel code is necessary
- Linux kernel developers and administrators should assess exposure and prioritize verification of affected systems
- The vulnerability has been resolved, but scope of affected systems and versions requires clarification
Technical summary
The Linux kernel vulnerability requires a BPF cpumask for bpf_cpumask_populate() to prevent verifier from accepting borrowed cpumask pointers as writable destinations. The vulnerability has been resolved, but scope of affected systems and versions requires clarification. Verification of BPF cpumask usage in kernel code is necessary. Linux kernel developers and administrators should assess exposure and prioritize verification of affected systems. The vulnerability requires attention from developers and administrators to assess exposure and prioritize verification of affected systems.
Defensive priority
Linux kernel developers and administrators should assess exposure and prioritize verification of affected systems.
Recommended defensive actions
- Review Linux kernel configurations and versions to determine exposure
- Verify BPF cpumask usage in kernel code
- Update kernel to latest version if necessary
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and versions is not explicitly stated. The vulnerability requires a BPF cpumask for bpf_cpumask_populate() to prevent verifier from accepting borrowed cpumask pointers as writable destinations. Linux kernel developers, administrators, and users who rely on Linux kernel-based systems should verify BPF cpumask usage in kernel code and assess exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-93112 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-93112
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-93112 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93112
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/0cfc9348a045da64955af2dd6902e66dfc7d6469
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/8740156ad33be5071b588b594c55f279457f667c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b7e2a5c6519adc73be55c3de2cb545e095a0fbc5
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.