Linux Kernel: security vulnerability (CVE-2025-21738)
Published Last modified Sources: SUSE, BSI, Debian LTS, Siemens ProductCERT, Red Hat, CVE.org, Msrc Update Guide, EUVD
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: ata: libata-sff: Ensure that we cannot write outside the allocated buffer reveliofuzzing reported that a SCSI_IOCTL_SEND_COMMAND ioctl with out_len set to 0xd42, SCSI command set to ATA_16 PASS-THROUGH, ATA command set to ATA_NOP, and protocol set to ATA_PROT_PIO, can cause ata_pio_sector() to write outside the allocated buffer, overwriting random memory. While a ATA device is supposed to abort a ATA_NOP command, there does seem to be a bug either in libata-sff or QEMU, where either this status is not set, or the status is cleared before read by ata_sff_hsm_move().
Update Linux Kernel to version 6.1.129, Linux Kernel to version 6.6.78, Linux Kernel to version 6.12.14.
- Affected
- Linux Kernel
lt 2.6.22..6.1.129 - Linux Kernel
lt 6.2..6.6.78 - Linux Kernel
lt 6.7..6.12.14 - Linux Kernel
lt 6.13..6.13.3
- Linux Kernel
- Fixed in
- Linux Kernel
6.1.129 - Linux Kernel
6.6.78 - Linux Kernel
6.12.14 - Linux Kernel
6.13.3 - Linux Kernel
6.14
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: SUSE, BSI, Debian LTS, Siemens ProductCERT, Red Hat, CVE.org, Msrc Update Guide, EUVD
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 13.1
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 48.38 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 13.1
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: ata: libata-sff: Ensure that we cannot write outside the allocated buffer reveliofuzzing reported that a SCSI_IOCTL_SEND_COMMAND ioctl with out_len set to 0xd42, SCSI command set to ATA_16 PASS-THROUGH, ATA command set to ATA_NOP, and protocol set to ATA_PROT_PIO, can cause ata_pio_sector() to write outside the allocated buffer, overwriting random memory. While a ATA device is supposed to abort a ATA_NOP command, there does seem to be a bug either in libata-sff or QEMU, where either this status is not set, or the status is cleared before read by ata_sff_hsm_move(). Anyway, that is most likely a separate bug. Looking at __atapi_pio_bytes(), it already has a safety check to ensure that __atapi_pio_bytes() cannot write outside the allocated buffer. Add a similar check to ata_pio_sector(), such that also ata_pio_sector() cannot write outside the allocated buffer.
Source: suse_csaf, BSI WID Portal, BSI CSAF, Debian LTS Advisories, siemens_advisory, redhat_csaf, cvelistv5, NVD (NIST), Microsoft Security Update Guide, CVE.org (MITRE), ENISA EUVD
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Dell | Secure Connect Gateway |
|
|
| IBM | Security Verify Access |
|
|
| Siemens | SIMATIC S7 |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux-6.1 | bullseye |
| Linux | linux | linux_kernel | — |
References & sources
- git.kernel.orgstable/c/a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c
- git.kernel.orgstable/c/d5e6e3000309359eae2a17117aa6e3c44897bf6c
- git.kernel.orgstable/c/0dd5aade301a10f4b329fa7454fdcc2518741902
- git.kernel.orgstable/c/0a17a9944b8d89ef03946121241870ac53ddaf45
- git.kernel.orgstable/c/6e74e53b34b6dec5a50e1404e2680852ec6768d2
- lists.debian.orgdebian-lts-announce/2025/03/msg00028.html
- Siemens ProductCERTproductcert/html/ssa-784472.html
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
New references:- https://git.kernel.org/stable/c/0a17a9944b8d89ef03946121241870ac53ddaf45
- https://git.kernel.org/stable/c/0dd5aade301a10f4b329fa7454fdcc2518741902
- https://git.kernel.org/stable/c/6e74e53b34b6dec5a50e1404e2680852ec6768d2
- https://git.kernel.org/stable/c/a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c
and 1 more reference
Show 15 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/0a17a9944b8d89ef03946121241870ac53ddaf45Reference added —https://git.kernel.org/stable/c/0dd5aade301a10f4b329fa7454fdcc2518741902Reference added —https://git.kernel.org/stable/c/6e74e53b34b6dec5a50e1404e2680852ec6768d2Reference added —https://git.kernel.org/stable/c/a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4cReference added —https://git.kernel.org/stable/c/d5e6e3000309359eae2a17117aa6e3c44897bf6cReference removed https://git.kernel.org/stable/c/0a17a9944b8d89ef03946121241870ac53ddaf45—Reference removed https://git.kernel.org/stable/c/0dd5aade301a10f4b329fa7454fdcc2518741902—Reference removed https://git.kernel.org/stable/c/6e74e53b34b6dec5a50e1404e2680852ec6768d2—Reference removed https://git.kernel.org/stable/c/a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c—Reference removed https://git.kernel.org/stable/c/d5e6e3000309359eae2a17117aa6e3c44897bf6c—Reference type removed https://git.kernel.org/stable/c/0a17a9944b8d89ef03946121241870ac53ddaf45 Types: Patch—Reference type removed https://git.kernel.org/stable/c/0dd5aade301a10f4b329fa7454fdcc2518741902 Types: Patch—Reference type removed https://git.kernel.org/stable/c/6e74e53b34b6dec5a50e1404e2680852ec6768d2 Types: Patch—Reference type removed https://git.kernel.org/stable/c/a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c Types: Patch—Reference type removed https://git.kernel.org/stable/c/d5e6e3000309359eae2a17117aa6e3c44897bf6c Types: Patch—Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedCVE Program
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://lists.debian.org/debian-lts-announce/2025/03/msg00028.htmlReference removed https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Record modifiedSiemens ADP
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2025/21xxx/CVE-2025-21738.json">CVE-2025-21738</a>Reference added —https://cert-portal.siemens.com/productcert/html/ssa-784472.htmlSource identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Record modifiedLinux
CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Show the original change
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2025-21738"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-21738.svg?lang=en" alt="CVE-2025-21738 – NEOSEC Intel" height="20"></a>