OESA-2026-2753 (CVE-2026-46294)
Vulnerability from osv_openeuler – Published: 2026-06-24 11:11 – Updated: 2026-08-06 11:11 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
dm: fix a buffer overflow in ioctl processing
Tony Asleson (using Claude) found a buffer overflow in dm-ioctl in the function retrieve_status:
- The code in retrieve_status checks that the output string fits into the output buffer and writes the output string there
- Then, the code aligns the "outptr" variable to the next 8-byte boundary: outptr = align_ptr(outptr);
- The alignment doesn't check overflow, so outptr could point past the buffer end
- The "for" loop is iterated again, it executes: remaining = len - (outptr - outbuf);
- If "outptr" points past "outbuf + len", the arithmetics wraps around and the variable "remaining" contains unusually high number
- With "remaining" being high, the code writes more data past the end of the buffer
Luckily, this bug has no security implications because: 1. Only root can issue device mapper ioctls 2. The commonly used libraries that communicate with device mapper (libdevmapper and devicemapper-rs) use buffer size that is aligned to 8 bytes - thus, "outptr = align_ptr(outptr)" can't overshoot the input buffer and the bug can't happen accidentally(CVE-2026-46294)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-debugsource-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-devel-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-source-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-tools-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"kernel-tools-devel-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"perf-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"perf-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"python2-perf-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"python3-perf-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2606.4.0.0377.oe2003sp4.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-debugsource-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-devel-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-source-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-tools-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"kernel-tools-devel-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"perf-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"perf-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"python2-perf-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"python3-perf-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2606.4.0.0377.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2606.4.0.0377.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm: fix a buffer overflow in ioctl processing\n\nTony Asleson (using Claude) found a buffer overflow in dm-ioctl in the\nfunction retrieve_status:\n\n1. The code in retrieve_status checks that the output string fits into\n the output buffer and writes the output string there\n2. Then, the code aligns the \u0026quot;outptr\u0026quot; variable to the next 8-byte\n boundary:\n\toutptr = align_ptr(outptr);\n3. The alignment doesn\u0026apos;t check overflow, so outptr could point past the\n buffer end\n4. The \u0026quot;for\u0026quot; loop is iterated again, it executes:\n\tremaining = len - (outptr - outbuf);\n5. If \u0026quot;outptr\u0026quot; points past \u0026quot;outbuf + len\u0026quot;, the arithmetics wraps around\n and the variable \u0026quot;remaining\u0026quot; contains unusually high number\n6. With \u0026quot;remaining\u0026quot; being high, the code writes more data past the end of\n the buffer\n\nLuckily, this bug has no security implications because:\n1. Only root can issue device mapper ioctls\n2. The commonly used libraries that communicate with device mapper\n (libdevmapper and devicemapper-rs) use buffer size that is aligned to\n 8 bytes - thus, \u0026quot;outptr = align_ptr(outptr)\u0026quot; can\u0026apos;t overshoot the input\n buffer and the bug can\u0026apos;t happen accidentally(CVE-2026-46294)",
"id": "OESA-2026-2753",
"modified": "2026-08-06T11:11:40Z",
"published": "2026-06-24T11:11:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2753"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46294"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2026-46294"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.