CVE-2022-50093: iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE)
Noroxi assessment
Priority: Monitor (action score 28/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.26% (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 0b4c0003aeda32a600f95df53b2848da8a5aa3fa, 5659efdadf04b56707d58c1b758df16d2e0eff2c, 73ce2046e04ad488cecc66757c36cbe1bdf089d4.
Low priority for now. Upgrade to Linux Linux 0b4c0003aeda32a600f95df53b2848da8a5aa3fa, 5659efdadf04b56707d58c1b758df16d2e0eff2c, 73ce2046e04ad488cecc66757c36cbe1bdf089d4 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: iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE) KASAN reports: [ 4.668325][ T0] BUG: KASAN: wild-memory-access in dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/asm/bitops.h:226 include/asm-generic/bitops/instrumented-non-atomic.h:142 include/linux/nodemask.h:415 drivers/iommu/intel/dmar.c:497) [ 4.676149][ T0] Read of size 8 at addr 1fffffff85115558 by task swapper/0/0 [ 4.683454][ T0] [ 4.685638][ T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.19.0-rc3-00004-g0e862838f290 #1 [ 4.694331][ T0] Hardware name: Supermicro SYS-5018D-FN4T/X10SDV-8C-TLN4F, BIOS 1.1 03/02/2016 [ 4.703196][ T0] Call Trace: [ 4.706334][ T0] <TASK> [ 4.709133][ T0] ? dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/asm/bitops.h:226 include/asm-generic/bitops/instrumented-non-atomic.h:142 include/linux/nodemask.h:415 drivers/iommu/intel/dmar.c:497) after converting the type of the first argument (@nr, bit number) of arch_test_bit() from `long` to `unsigned long`[0]. Under certain conditions (for example, when ACPI NUMA is disabled via command line), pxm_to_node() can return %NUMA_NO_NODE (-1). It is valid 'magic' number of NUMA node, but not valid bit number to use in bitops. node_online() eventually descends to test_bit() without checking for the input, assuming it's on caller side (which might be good for perf-critical tasks). There, -1 becomes %ULONG_MAX which leads to an insane array index when calculating bit position in memory. For now, add an explicit check for @node being not %NUMA_NO_NODE before calling test_bit(). The actual logics didn't change here at all. [0] https://github.com/norov/linux/commit/0e862838f290147ea9c16db852d8d494b552d38d
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 kernel2.6.33 and later · before 5.4.211
- linux linux kernel5.5 and later · before 5.10.137
- linux linux kernel5.11 and later · before 5.15.61
- linux linux kernel5.16 and later · before 5.18.18
- linux linux kernel5.19 and later · before 5.19.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
- 2.6.33affected
- ee34b32d8c2950f66038c8975747ef9aec855289 and later · before b12304984654d8e58a2b22ff94c4410906d6267faffected · git
- ee34b32d8c2950f66038c8975747ef9aec855289 and later · before 5659efdadf04b56707d58c1b758df16d2e0eff2caffected · git
- ee34b32d8c2950f66038c8975747ef9aec855289 and later · before 0b4c0003aeda32a600f95df53b2848da8a5aa3faaffected · git
- ee34b32d8c2950f66038c8975747ef9aec855289 and later · before 73ce2046e04ad488cecc66757c36cbe1bdf089d4affected · git
- ee34b32d8c2950f66038c8975747ef9aec855289 and later · before c2304c50f4d94f56c2e326f25c9dc8cf2ba6f5faaffected · git
- ee34b32d8c2950f66038c8975747ef9aec855289 and later · before b0b0b77ea611e3088e9523e60860f4f41b62b235affected · git
- before 2.6.33not affected · semver
- 5.4.211 and later · up to and including 5.4.*not affected · semver
- 5.10.137 and later · up to and including 5.10.*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 | before 6.0.2-1 | 6.0.2-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-2022-50090Jun 18, 2025 · btrfs: replace BTRFS_MAX_EXTENT_SIZE with fs_info->max_extent_size31Monitor
- ← EarlierCVE-2022-50092Jun 18, 2025 · dm thin: fix use-after-free crash in dm_sm_register_threshold_callback22Monitor
- Later →CVE-2022-50094Jun 18, 2025 · spmi: trace: fix stack-out-of-bound access in SPMI tracing functions28Monitor
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 | 0b4c0003aeda32a600f95df53b2848da8a5aa3fa | Vendor (CNA) |
| Linux Linux | 5659efdadf04b56707d58c1b758df16d2e0eff2c | Vendor (CNA) |
| Linux Linux | 73ce2046e04ad488cecc66757c36cbe1bdf089d4 | Vendor (CNA) |
| Linux Linux | b0b0b77ea611e3088e9523e60860f4f41b62b235 | Vendor (CNA) |
| Linux Linux | b12304984654d8e58a2b22ff94c4410906d6267f | Vendor (CNA) |
| Linux Linux | c2304c50f4d94f56c2e326f25c9dc8cf2ba6f5fa | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | 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).
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
- high · data can be read
- 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
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5659efdadf04b56707d58c1b758df16d2e0eff2c
- git.kernel.org/stable/c/73ce2046e04ad488cecc66757c36cbe1bdf089d4
- git.kernel.org/stable/c/b0b0b77ea611e3088e9523e60860f4f41b62b235
- git.kernel.org/stable/c/b12304984654d8e58a2b22ff94c4410906d6267f
- git.kernel.org/stable/c/c2304c50f4d94f56c2e326f25c9dc8cf2ba6f5fa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.