Linux Kernel up to 6.12.41/6.15.9/6.16.0 parse_longname memory corruption

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

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.12.41/6.15.9/6.16.0 and classified as critical. The affected element is the function parse_longname. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2025-38660. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.41/6.15.9/6.16.0 and classified as critical. This issue affects the function parse_longname. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: [ceph] parse_longname(): strrchr() expects NUL-terminated string ... and parse_longname() is not guaranteed that. That's the reason why it uses kmemdup_nul() to build the argument for kstrtou64(); the problem is, kstrtou64() is not the only thing that need it. Just get a NUL-terminated copy of the entire thing and be done with that...

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2025-38660 since 04/16/2025. The exploitation is known to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/29/2026).

The vulnerability scanner Nessus provides a plugin with the ID 266176 (Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2025-1208)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.42, 6.15.10, 6.16.1 or 6.17-rc1 eliminates this vulnerability. Applying the patch bb80f7618832d26f7e395f52f82b1dac76223e5f/3145b2b11492d61c512bbc59660bb823bc757f48/493479af8af3ab907f49e99323777d498a4fbd2b/101841c38346f4ca41dc1802c867da990ffb32eb 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 (266176) and CERT Bund (WID-SEC-2025-1898). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Debian Linux
  • Google Cloud Platform
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • NetApp AFF
  • NetApp ActiveIQ Unified Manager
  • SUSE openSUSE
  • Dell Avamar
  • NetApp FAS
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway
  • Dell ECS

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
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: Memory corruption
CWE: CWE-119
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: 266176
Nessus Name: Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2025-1208)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.42/6.15.10/6.16.1/6.17-rc1
Patch: bb80f7618832d26f7e395f52f82b1dac76223e5f/3145b2b11492d61c512bbc59660bb823bc757f48/493479af8af3ab907f49e99323777d498a4fbd2b/101841c38346f4ca41dc1802c867da990ffb32eb

Timelineinfo

04/16/2025 CVE reserved
08/22/2025 +128 days Advisory disclosed
08/22/2025 +0 days VulDB entry created
05/29/2026 +280 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38660 (🔒)
GCVE (CVE): GCVE-0-2025-38660
GCVE (VulDB): GCVE-100-321107
CERT Bund: WID-SEC-2025-1898 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und Privilegieneskalation

Entryinfo

Created: 08/22/2025 23:35
Updated: 05/29/2026 04:47
Changes: 08/22/2025 23:35 (58), 09/22/2025 03:57 (7), 09/30/2025 23:03 (2), 10/18/2025 06:58 (1), 10/26/2025 09:51 (1), 11/26/2025 13:49 (12), 12/13/2025 13:17 (1), 02/14/2026 07:44 (1), 05/29/2026 04:47 (3)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!