-
CVE-2026-43073
- EPSS 0.02%
- Veröffentlicht 05.05.2026 16:16:16
- Zuletzt bearbeitet 06.05.2026 13:08:07
- Quelle 416baaa9-dc9f-4396-8d5f-8c081f
- CVE-Watchlists
- Unerledigt
x86-64: rename misleadingly named '__copy_user_nocache()' function
In the Linux kernel, the following vulnerability has been resolved: x86-64: rename misleadingly named '__copy_user_nocache()' function This function was a masterclass in bad naming, for various historical reasons. It claimed to be a non-cached user copy. It is literally _neither_ of those things. It's a specialty memory copy routine that uses non-temporal stores for the destination (but not the source), and that does exception handling for both source and destination accesses. Also note that while it works for unaligned targets, any unaligned parts (whether at beginning or end) will not use non-temporal stores, since only words and quadwords can be non-temporal on x86. The exception handling means that it _can_ be used for user space accesses, but not on its own - it needs all the normal "start user space access" logic around it. But typically the user space access would be the source, not the non-temporal destination. That was the original intention of this, where the destination was some fragile persistent memory target that needed non-temporal stores in order to catch machine check exceptions synchronously and deal with them gracefully. Thus that non-descriptive name: one use case was to copy from user space into a non-cached kernel buffer. However, the existing users are a mix of that intended use-case, and a couple of random drivers that just did this as a performance tweak. Some of those random drivers then actively misused the user copying version (with STAC/CLAC and all) to do kernel copies without ever even caring about the exception handling, _just_ for the non-temporal destination. Rename it as a first small step to actually make it halfway sane, and change the prototype to be more normal: it doesn't take a user pointer unless the caller has done the proper conversion, and the argument size is the full size_t (it still won't actually copy more than 4GB in one go, but there's also no reason to silently truncate the size argument in the caller). Finally, use this now sanely named function in the NTB code, which mis-used a user copy version (with STAC/CLAC and all) of this interface despite it not actually being a user copy at all.
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerLinux
≫
Produkt
Linux
Default Statusunaffected
Version
06917f753547e6bba8a5d17f79971d1c071a70dd
Version <
14b9194db4a28421a4dbe5d6e519efbaa7c5f3cd
Status
affected
Version
06917f753547e6bba8a5d17f79971d1c071a70dd
Version <
c6d4e0599e7e73abc04e2488dfeb7940c4039660
Status
affected
Version
06917f753547e6bba8a5d17f79971d1c071a70dd
Version <
d993e1723aa2a085aa0d72e70ea889031fc225b4
Status
affected
Version
06917f753547e6bba8a5d17f79971d1c071a70dd
Version <
efea91ad1729ff1853d7418e4d3bc27d085e72d0
Status
affected
Version
06917f753547e6bba8a5d17f79971d1c071a70dd
Version <
d187a86de793f84766ea40b9ade7ac60aabbb4fe
Status
affected
HerstellerLinux
≫
Produkt
Linux
Default Statusaffected
Version
4.2
Status
affected
Version
0
Version <
4.2
Status
unaffected
Version <=
6.12.*
Version
6.12.83
Status
unaffected
Version <=
6.18.*
Version
6.18.24
Status
unaffected
Version <=
6.19.*
Version
6.19.14
Status
unaffected
Version <=
7.0.*
Version
7.0.1
Status
unaffected
Version <=
*
Version
7.1-rc1
Status
unaffected
VulnDex Vulnerability Enrichment
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.02% | 0.067 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|