Skip to content
Noroxi
CVE-2025-71199· NVD / CVE Program· CNA Linux

iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver

Noroxi assessment

Priority: Monitor (action score 0/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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 4c83dd62595ee7b7c9298a4d19a256b6647e7240, 919d176b05776c7ede79c36744c823a07d631617, 9795fe80976f8c31cafda7d44edfc0f532d1f7c4.

Low priority for now. Upgrade to Linux Linux 4c83dd62595ee7b7c9298a4d19a256b6647e7240, 919d176b05776c7ede79c36744c823a07d631617, 9795fe80976f8c31cafda7d44edfc0f532d1f7c4 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: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver at91_adc_interrupt can call at91_adc_touch_data_handler function to start the work by schedule_work(&st->touch_st.workq). If we remove the module which will call at91_adc_remove to make cleanup, it will free indio_dev through iio_device_unregister but quite a bit later. While the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | at91_adc_workq_handler at91_adc_remove | iio_device_unregister(indio_dev) | //free indio_dev a bit later | | iio_push_to_buffers(indio_dev) | //use indio_dev Fix it by ensuring that the work is canceled before proceeding with the cleanup in at91_adc_remove.

—No exploit Fix available
Published
Feb 4, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
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.

Follow CVE-2025-71199

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

—

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.19affected
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before 4c83dd62595ee7b7c9298a4d19a256b6647e7240affected · git
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before fdc8c835c637a3473878d1e7438c77ab8928af63affected · git
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before 919d176b05776c7ede79c36744c823a07d631617affected · git
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before 9795fe80976f8c31cafda7d44edfc0f532d1f7c4affected · git
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before d7b6fc224c7f5d6d8adcb18037138d3cfe2bbdfeaffected · git
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before d890234a91570542c228a20f132ce74f9fedd904affected · git
    • 23ec2774f1cc168b1f32a2e0ed2709cb473bb94e and later · before dbdb442218cd9d613adeab31a88ac973f22c4873affected · git
    • before 4.19not affected · semver
    • 5.10.249 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-71196Feb 4, 2026 · phy: stm32-usphyc: Fix off by one in probe()
    0Monitor
  • ← EarlierCVE-2025-71198Feb 4, 2026 · iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection
    0Monitor
  • Later →CVE-2026-23049Feb 4, 2026 · drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4c83dd62595ee7b7c9298a4d19a256b6647e7240Vendor (CNA)
Linux Linux919d176b05776c7ede79c36744c823a07d631617Vendor (CNA)
Linux Linux9795fe80976f8c31cafda7d44edfc0f532d1f7c4Vendor (CNA)
Linux Linuxd7b6fc224c7f5d6d8adcb18037138d3cfe2bbdfeVendor (CNA)
Linux Linuxd890234a91570542c228a20f132ce74f9fedd904Vendor (CNA)
Linux Linuxdbdb442218cd9d613adeab31a88ac973f22c4873Vendor (CNA)
Linux Linuxfdc8c835c637a3473878d1e7438c77ab8928af63Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Finders, 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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records