CVE-2026-43433
Last modified
CVE-2026-43433 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: rust_binder: avoid reading the written value in offsets array When sending a transaction, its offsets array is first copied into the target proc's vma, and then the values are read back from there. This is normally fine because the vma is a read-only mapping, so the target process cannot change the value under us. However, if the target process somehow gains the ability to write to its own vma, it could change the offset before it's read back, causing the kernel to misinterpret what the sender meant. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: rust_binder: avoid reading the written value in offsets array When sending a transaction, its offsets array is first copied into the target proc's vma, and then the values are read back from there. This is normally fine because the vma is a read-only mapping, so the target process cannot change the value under us. However, if the target process somehow gains the ability to write to its own vma, it could change the offset before it's read back, causing the kernel to misinterpret what the sender meant. If the sender happens to send a payload with a specific shape, this could in the worst case lead to the receiver being able to privilege escalate into the sender. The intent is that gaining the ability to change the read-only vma of your own process should not be exploitable, so remove this TOCTOU read even though it's unexploitable without another Binder bug.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.18, < 6.18.19 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.9 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43433?
How severe is CVE-2026-43433?
How do I fix CVE-2026-43433?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-43427In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-43428In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43429In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43430In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-43431In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43432In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43434In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43435In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43436In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43437In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43438In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43439In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2026-43433?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
