Linux Kernel up to 6.6.121/6.12.67/6.18.7/6.19-rc6 adc sama5d2_adc use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.121/6.12.67/6.18.7/6.19-rc6. It has been classified as critical. This issue affects the function sama5d2_adc of the component adc. This manipulation causes use after free. This vulnerability appears as CVE-2025-71199. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.121/6.12.67/6.18.7/6.19-rc6. It has been declared as critical. Affected by this vulnerability is the function sama5d2_adc of the component adc. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2025-71199 since 01/31/2026. The exploitation appears to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/30/2026).

The vulnerability scanner Nessus provides a plugin with the ID 297913 (Linux Distros Unpatched Vulnerability : CVE-2025-71199), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.122, 6.12.68, 6.18.8 or 6.19-rc7 eliminates this vulnerability. Applying the patch 9795fe80976f8c31cafda7d44edfc0f532d1f7c4/d7b6fc224c7f5d6d8adcb18037138d3cfe2bbdfe/d890234a91570542c228a20f132ce74f9fedd904/dbdb442218cd9d613adeab31a88ac973f22c4873 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (297913) and CERT Bund (WID-SEC-2026-0324). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Google Cloud Platform
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 297913
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-71199

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.122/6.12.68/6.18.8/6.19-rc7
Patch: 9795fe80976f8c31cafda7d44edfc0f532d1f7c4/d7b6fc224c7f5d6d8adcb18037138d3cfe2bbdfe/d890234a91570542c228a20f132ce74f9fedd904/dbdb442218cd9d613adeab31a88ac973f22c4873

Timelineinfo

01/31/2026 CVE reserved
02/04/2026 +4 days Advisory disclosed
02/04/2026 +0 days VulDB entry created
04/30/2026 +85 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-71199 (🔒)
GCVE (CVE): GCVE-0-2025-71199
GCVE (VulDB): GCVE-100-344293
CERT Bund: WID-SEC-2026-0324 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 02/04/2026 18:03
Updated: 04/30/2026 03:29
Changes: 02/04/2026 18:03 (59), 02/05/2026 15:20 (7), 02/06/2026 14:42 (2), 04/30/2026 03:29 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!