CVE-2026-43073: x86-64: rename misleadingly named '__copy_user_nocache()' function
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 14b9194db4a28421a4dbe5d6e519efbaa7c5f3cd, 73c2dc2c14d6a2efa5dde469546a907482af07fe, c6d4e0599e7e73abc04e2488dfeb7940c4039660.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 14b9194db4a28421a4dbe5d6e519efbaa7c5f3cd, 73c2dc2c14d6a2efa5dde469546a907482af07fe, c6d4e0599e7e73abc04e2488dfeb7940c4039660 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 5, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.2.1 and later · before 6.12.83
- linux linux kernel6.13 and later · before 6.18.24
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel7.0 and later · before 7.0.1
- linux linux kernel4.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.2affected
- 06917f753547e6bba8a5d17f79971d1c071a70dd and later · before 73c2dc2c14d6a2efa5dde469546a907482af07feaffected · git
- 06917f753547e6bba8a5d17f79971d1c071a70dd and later · before 14b9194db4a28421a4dbe5d6e519efbaa7c5f3cdaffected · git
- 06917f753547e6bba8a5d17f79971d1c071a70dd and later · before c6d4e0599e7e73abc04e2488dfeb7940c4039660affected · git
- 06917f753547e6bba8a5d17f79971d1c071a70dd and later · before d993e1723aa2a085aa0d72e70ea889031fc225b4affected · git
- 06917f753547e6bba8a5d17f79971d1c071a70dd and later · before efea91ad1729ff1853d7418e4d3bc27d085e72d0affected · git
- 06917f753547e6bba8a5d17f79971d1c071a70dd and later · before d187a86de793f84766ea40b9ade7ac60aabbb4feaffected · git
- before 4.2not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.83 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43067May 5, 2026 · ext4: handle wraparound when searching for blocks for indirect mapped blocks39Monitor
- ← EarlierCVE-2026-43071May 5, 2026 · dcache: Limit the minimal number of bucket to two36Monitor
- Later →CVE-2026-43075May 6, 2026 · ocfs2: fix out-of-bounds write in ocfs2_write_end_inline31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 14b9194db4a28421a4dbe5d6e519efbaa7c5f3cd | Vendor (CNA) |
| Linux Linux | 73c2dc2c14d6a2efa5dde469546a907482af07fe | Vendor (CNA) |
| Linux Linux | c6d4e0599e7e73abc04e2488dfeb7940c4039660 | Vendor (CNA) |
| Linux Linux | d187a86de793f84766ea40b9ade7ac60aabbb4fe | Vendor (CNA) |
| Linux Linux | d993e1723aa2a085aa0d72e70ea889031fc225b4 | Vendor (CNA) |
| Linux Linux | efea91ad1729ff1853d7418e4d3bc27d085e72d0 | Vendor (CNA) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0171 · May 6, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/73c2dc2c14d6a2efa5dde469546a907482af07fe
- git.kernel.org/stable/c/c6d4e0599e7e73abc04e2488dfeb7940c4039660
- git.kernel.org/stable/c/d187a86de793f84766ea40b9ade7ac60aabbb4fe
- git.kernel.org/stable/c/d993e1723aa2a085aa0d72e70ea889031fc225b4
- git.kernel.org/stable/c/efea91ad1729ff1853d7418e4d3bc27d085e72d0
- project-zero.issues.chromium.org/issues/496923375
Vendor advisories and official records. Exploit/PoC links are deliberately left out.