CVE-2026-31768: iio: adc: ti-adc161s626: use DMA-safe memory for spi_read()
Noroxi assessment
Priority: Monitor (action score 31/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.13% (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 014c6d27878d3883f7bb065610768fd021de1a96, 67b3a91bdc48220bfb67155ab528121b9c822782, 768461517a28d80fe81ea4d5d03a90cd184ea6ad.
Low priority for now. Upgrade to Linux Linux 014c6d27878d3883f7bb065610768fd021de1a96, 67b3a91bdc48220bfb67155ab528121b9c822782, 768461517a28d80fe81ea4d5d03a90cd184ea6ad 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: iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() Add a DMA-safe buffer and use it for spi_read() instead of a stack memory. All SPI buffers must be DMA-safe. Since we only need up to 3 bytes, we just use a u8[] instead of __be16 and __be32 and change the conversion functions appropriately.
- Published
- May 1, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.9 and later · before 6.1.168
- linux linux kernel6.2 and later · before 6.6.134
- linux linux kernel6.7 and later · before 6.12.81
- linux linux kernel6.13 and later · before 6.18.22
- linux linux kernel6.19 and later · before 6.19.12
- linux linux kernel7.0
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.9affected
- 4d671b71beefbfc145b971a11e0c3cabde94b673 and later · before b3bb8faeca1a2ef7be95ee8a512b639f9ffce947affected · git
- 4d671b71beefbfc145b971a11e0c3cabde94b673 and later · before fa64aab25aba47296aa8d12bb4c88ec3fecb2054affected · git
- 4d671b71beefbfc145b971a11e0c3cabde94b673 and later · before 67b3a91bdc48220bfb67155ab528121b9c822782affected · git
- 4d671b71beefbfc145b971a11e0c3cabde94b673 and later · before 014c6d27878d3883f7bb065610768fd021de1a96affected · git
- 4d671b71beefbfc145b971a11e0c3cabde94b673 and later · before d2d031b0786ea66ab0577c9d2d71435068d32199affected · git
- 4d671b71beefbfc145b971a11e0c3cabde94b673 and later · before 768461517a28d80fe81ea4d5d03a90cd184ea6adaffected · git
- before 4.9not affected · semver
- 6.1.168 and later · up to and including 6.1.*not affected · semver
- 6.6.134 and later · up to and including 6.6.*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.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.12-1 | 6.19.12-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-31761May 1, 2026 · iio: gyro: mpu3050: Move iio_device_register() to correct location31Monitor
- ← EarlierCVE-2026-31767May 1, 2026 · drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode22Monitor
- Later →CVE-2026-31771May 1, 2026 · Bluetooth: hci_event: move wake reason storage into validated event handlers32Monitor
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 | 014c6d27878d3883f7bb065610768fd021de1a96 | Vendor (CNA) |
| Linux Linux | 67b3a91bdc48220bfb67155ab528121b9c822782 | Vendor (CNA) |
| Linux Linux | 768461517a28d80fe81ea4d5d03a90cd184ea6ad | Vendor (CNA) |
| Linux Linux | b3bb8faeca1a2ef7be95ee8a512b639f9ffce947 | Vendor (CNA) |
| Linux Linux | d2d031b0786ea66ab0577c9d2d71435068d32199 | Vendor (CNA) |
| Linux Linux | fa64aab25aba47296aa8d12bb4c88ec3fecb2054 | Vendor (CNA) |
| debian:linux | 6.1.170-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
- high · data or configuration can be modified
- 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
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (8 more)Show less
- git.kernel.org/stable/c/67b3a91bdc48220bfb67155ab528121b9c822782
- git.kernel.org/stable/c/768461517a28d80fe81ea4d5d03a90cd184ea6ad
- git.kernel.org/stable/c/b3bb8faeca1a2ef7be95ee8a512b639f9ffce947
- git.kernel.org/stable/c/d2d031b0786ea66ab0577c9d2d71435068d32199
- git.kernel.org/stable/c/fa64aab25aba47296aa8d12bb4c88ec3fecb2054
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.