Linux Kernel up to 6.1.146/6.6.99/6.12.39/6.15.7 Subdevice Driver comedi_fops.c insn_rw_emulate_bits uninitialized pointer

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.
5.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.1.146/6.6.99/6.12.39/6.15.7. Affected by this vulnerability is the function insn_rw_emulate_bits of the file comedi_fops.c of the component Subdevice Driver. Such manipulation leads to uninitialized pointer. This vulnerability is referenced as CVE-2025-38480. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.1.146/6.6.99/6.12.39/6.15.7. Affected by this issue is the function insn_rw_emulate_bits of the file comedi_fops.c of the component Subdevice Driver. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. Using CWE to declare the problem leads to CWE-824. The product accesses or uses a pointer that has not been initialized. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: comedi: Fix use of uninitialized data in insn_rw_emulate_bits() For Comedi `INSN_READ` and `INSN_WRITE` instructions on "digital" subdevices (subdevice types `COMEDI_SUBD_DI`, `COMEDI_SUBD_DO`, and `COMEDI_SUBD_DIO`), it is common for the subdevice driver not to have `insn_read` and `insn_write` handler functions, but to have an `insn_bits` handler function for handling Comedi `INSN_BITS` instructions. In that case, the subdevice's `insn_read` and/or `insn_write` function handler pointers are set to point to the `insn_rw_emulate_bits()` function by `__comedi_device_postconfig()`. For `INSN_WRITE`, `insn_rw_emulate_bits()` currently assumes that the supplied `data[0]` value is a valid copy from user memory. It will at least exist because `do_insnlist_ioctl()` and `do_insn_ioctl()` in "comedi_fops.c" ensure at lease `MIN_SAMPLES` (16) elements are allocated. However, if `insn->n` is 0 (which is allowable for `INSN_READ` and `INSN_WRITE` instructions, then `data[0]` may contain uninitialized data, and certainly contains invalid data, possibly from a different instruction in the array of instructions handled by `do_insnlist_ioctl()`. This will result in an incorrect value being written to the digital output channel (or to the digital input/output channel if configured as an output), and may be reflected in the internal saved state of the channel. Fix it by returning 0 early if `insn->n` is 0, before reaching the code that accesses `data[0]`. Previously, the function always returned 1 on success, but it is supposed to be the number of data samples actually read or written up to `insn->n`, which is 0 in this case.

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2025-38480 since 04/16/2025. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 270134 (Debian dla-4328 : linux-config-6.1 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.147, 6.6.100, 6.12.40 or 6.15.8 eliminates this vulnerability. Applying the patch 3050d197d6bc9ef128944a70210f42d2430b3000/10f9024a8c824a41827fff1fefefb314c98e2c88/2af1e7d389c2619219171d23f5b96dbcbb7f9656/3ab55ffaaf75d0c7b68e332c1cdcc1b0e0044870/e9cb26291d009243a4478a7ffb37b3a9175bfce9 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 (270134) and CERT Bund (WID-SEC-2025-1665). Once again VulDB remains the best source for vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • RESF Rocky Linux
  • Dell Avamar
  • NetApp ActiveIQ Unified Manager
  • Dell PowerProtect Data Domain
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway
  • IBM Security Verify Access

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

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

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

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 270134
Nessus Name: Debian dla-4328 : linux-config-6.1 - security update

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.147/6.6.100/6.12.40/6.15.8
Patch: 3050d197d6bc9ef128944a70210f42d2430b3000/10f9024a8c824a41827fff1fefefb314c98e2c88/2af1e7d389c2619219171d23f5b96dbcbb7f9656/3ab55ffaaf75d0c7b68e332c1cdcc1b0e0044870/e9cb26291d009243a4478a7ffb37b3a9175bfce9

Timelineinfo

04/16/2025 CVE reserved
07/28/2025 +103 days Advisory disclosed
07/28/2025 +0 days VulDB entry created
01/25/2026 +181 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38480 (🔒)
GCVE (CVE): GCVE-0-2025-38480
GCVE (VulDB): GCVE-100-317900
CERT Bund: WID-SEC-2025-1665 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 07/28/2025 14:52
Updated: 01/25/2026 15:00
Changes: 07/28/2025 14:52 (59), 08/17/2025 20:34 (7), 08/19/2025 11:11 (1), 08/24/2025 00:13 (1), 08/26/2025 18:42 (1), 10/01/2025 06:01 (1), 10/14/2025 06:05 (2), 10/18/2025 10:01 (1), 11/02/2025 03:55 (1), 11/16/2025 21:41 (1), 01/07/2026 17:46 (11), 01/25/2026 15:00 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

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!