dbcve.org
Linux KernelOperating system · Linux

CVE-2025-38485

HIGH · 7.8 CVSS v3.1 Published 2025-07-28
Fix available
A fix is available. Upgrade to 6.1.147 / 6.6.100 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush fxls8962af_fifo_flush() uses indio_dev->active_scan_mask (with iio_for_each_active_channel()) without making sure the indio_dev stays in buffer mode. There is a race if indio_dev exits buffer mode in the middle of the interrupt that flushes the fifo. Fix this by calling synchronize_irq() to ensure that no interrupt is currently running when disabling buffer mode. Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read [...] _find_first_bit_le from fxls8962af_fifo_flush+0x17c/0x290 fxls8962af_fifo_flush from fxls8962af_interrupt+0x80/0x178 fxls8962af_interrupt from irq_thread_fn+0x1c/0x7c irq_thread_fn from irq_thread+0x110/0x1f4 irq_thread from kthread+0xe0/0xfc kthread from ret_from_fork+0x14/0x2c

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.14, < 6.1.147>= 6.2, < 6.6.100>= 6.7, < 6.12.40>= 6.13, < 6.15.8= 6.16
Debian LinuxOperating system
Affected:= 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.147 / 6.6.100 / 6.12.40 or later
Fixed in 6.1.1476.6.1006.12.40
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 6.1.147 (for 5.14-6.1.x), 6.6.100 (for 6.2-6.6.x), 6.12.40 (for 6.7-6.12.x), or 6.15.8 (for 6.13+). For Debian 11, apply Debian kernel security updates.

  1. 1. Identify the currently running kernel version using 'uname -r'
  2. 2. Check if the running kernel version is affected: >= 5.14 and < 6.1.147, OR >= 6.2 and < 6.6.100, OR >= 6.7 and < 6.12.40, OR >= 6.13 and < 6.15.8
  3. 3. For Debian 11 systems: check for available kernel updates via 'apt update && apt list --upgradable' or 'apt-cache policy linux-image-*'
  4. 4. Apply the appropriate kernel upgrade: for Debian 11, upgrade to a patched version available through Debian security updates
  5. 5. For upstream Linux: upgrade to one of the fixed releases: 6.1.147, 6.6.100, 6.12.40, or 6.15.8 (depending on which stable branch you are on)
  6. 6. Reboot the system to load the fixed kernel
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with third-party kernel modules or proprietary drivers. Ensure backups and test in staging if possible.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-38485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-38485 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data