PatchSiren cyber security CVE debrief
CVE-2026-90358 Linux CVE debrief
A vulnerability in the Linux kernel's bpf subsystem has been resolved. The `btf_distill_func_proto` function accepts a function argument up to 16 bytes, but the current implementation assumes an __int128 argument only needs one register. This under-allocation causes the `save_args` function to overwrite adjacent stack slots. The vulnerability affects Linux kernel versions and maintainers should assess exposure and prioritize verification of affected systems. The issue is caused by an under-allocated register save area for 128-bit arguments, which can lead to adjacent stack slots being overwritten.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- 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 maintainers, Linux system administrators, and security teams responsible for Linux systems should assess exposure and prioritize verification of affected systems. Linux kernel users and operators should review Linux kernel configurations and versions to determine exposure and verify system registry and loaded modules for potential indicators of compromise.
Why it matters
A vulnerability in the Linux kernel's bpf subsystem has been resolved. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.
- Verify Linux kernel configurations and versions to determine exposure
- Monitor system logs for suspicious activity
- Update to the latest Linux kernel version if possible
Technical summary
The Linux kernel's bpf subsystem has a vulnerability caused by an under-allocated register save area for 128-bit arguments. This can lead to adjacent stack slots being overwritten. The `btf_distill_func_proto` function accepts a function argument up to 16 bytes, but the current implementation assumes an __int128 argument only needs one register. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems. The vulnerability affects Linux kernel versions and maintainers should review compensating controls for exposed systems while remediation is scheduled and verified.
Defensive priority
Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.
Recommended defensive actions
- Review Linux kernel configurations and versions to determine exposure
- Verify system registry and loaded modules for potential indicators of compromise
- Update to the latest Linux kernel version if possible
- Monitor system logs for suspicious activity
- 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.
- 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. Linux kernel maintainers and users should verify Linux kernel configurations and versions to determine exposure. The vulnerability has been resolved in the Linux kernel, but the exact versions affected are not specified. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90358 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90358
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90358 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90358
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/40f3bfbbb222b92278f3797614b70f68d46824ac
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4aed2346fa9b88d458eeb8c01123f3c07585a675
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/814cba835ef648e0c5eb79505c96c0493b29eea6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/a6d7d7a253c550e74b0651897fe313c2f9b2301f
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.