rust_binder: avoid reading the written value in offsets array
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.19, 6.19.9
- CVEs
- CVE-2026-43433
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 13:37 UTC · Revision 1
Source evidence
rust_binder: avoid reading the written value in offsets array
core-osv · Original sourcePublished 8 May 2026, 14:22 UTC
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.
osv:CVE-2026-43433
Kernel
Fixed versions: 6.18.19, 6.19.9
Complete source record
{
"id": "92a4c76efae932c0a39f4e6a17cfcfeb6b16a61cb5d4b56e8f22f524f4d362c3",
"url": "https://osv.dev/vulnerability/CVE-2026-43433",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "rust_binder: avoid reading the written value in offsets array",
"summary": "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.",
"evidence": "osv:CVE-2026-43433",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.19",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-43433",
"aliases": [
"CVE-2026-43433"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "eafedbc7c050c44744fbdf80bdf3315e860b7513"
},
{
"fixed": "e19afb53f7723b3bd22224f2b0c7dcfa70bb973f"
},
{
"fixed": "3672141c93b7a0c0132bf5d5021a4b7f1d663aaa"
},
{
"fixed": "4cb9e13fec0de7c942f5f927469beb8e48ddd20f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43433.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.18.0"
},
{
"fixed": "6.18.19"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43433.json"
}
}
],
"modified": "2026-10-28T02:30:29.243658065Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3672141c93b7a0c0132bf5d5021a4b7f1d663aaa",
"https://git.kernel.org/stable/c/4cb9e13fec0de7c942f5f927469beb8e48ddd20f",
"https://git.kernel.org/stable/c/e19afb53f7723b3bd22224f2b0c7dcfa70bb973f",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43433.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-43433",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43433.json"
}
},
"related_cves": [
{
"value": "CVE-2026-43433",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 495986,
"published_at": "2026-05-08T14:22:04.632+00:00"
}