CVE-2026-46029
- Source
- https://cve.org/CVERecord?id=CVE-2026-46029
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-46029.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-46029
- Downstream
- Related
- Published
- 2026-05-27T12:56:38.376Z
- Modified
- 2026-06-18T03:56:52.433920341Z
- Severity
-
- 7.0 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- mm/slab: return NULL early from kmalloc_nolock() in NMI on UP
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
mm/slab: return NULL early from kmalloc_nolock() in NMI on UP
On UP kernels (!CONFIGSMP), spintrylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, kmallocnolock() called from NMI context can re-enter the slab allocator and acquire n->listlock that the interrupted context is already holding, corrupting slab state.
With CONFIGDEBUGSPINLOCK on UP, the following BUG is triggered with the slub_kunit test module:
BUG: spinlock trylock failure on UP on CPU#0, kunittrycatch/243 [...] Call Trace: <NMI> dumpstacklvl+0x3f/0x60 dorawspintrylock+0x41/0x50 rawspintrylock+0x24/0x50 getfrompartial_node+0x120/0x4d0 __slaballoc+0x8a/0x4c0 kmallocnolocknoprof+0x164/0x310 [...] </NMI>
Fix this by returning NULL early when invoked from NMI on a UP kernel.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46029.json" }- References
-
- https://git.kernel.org/stable/c/5b31044e649e3e54c2caef135c09b371c2fbcd08
- https://git.kernel.org/stable/c/a8d95d274be241ad21f6523bf2d6ba0d7d7e46b7
- https://git.kernel.org/stable/c/d66553204a15bdb257d9ef8aca1e12f5fbb910b2
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46029.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-46029
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git