Evidence used
- CISA confirms exploitation in the wild.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 3.25% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-39682High confidence
Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability
Linux · Kernel
9.8CriticalCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productCISA confirms exploitation in the wild and lists 2026-09-21 as the remediation due date. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Linux Kernel and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Canonical Ubuntu Security: 20 affected package states with no published fix
Distribution package intelligence
24 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.12.48-1 | Debian Security Tracker ↗Source updated 29 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.1.153-1 | Debian Security Tracker ↗Source updated 29 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.16.5-1 | Debian Security Tracker ↗Source updated 29 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.16.5-1 | Debian Security Tracker ↗Source updated 29 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-aws | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-nvidia | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gcp | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gke | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gkeop | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-ibm | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-intel | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-lowlatency | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-lowlatency | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-tegra | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oem-6.11 | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oracle | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-riscv | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-xilinx | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 28 Oct 2026 |
Direct vendor intelligence
3 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2025-39682 · CSAF 2.0 · revision 63 · interimSUSE Product Security TeamCVE-2025-39682
The vendor explicitly identifies these products as affected by this CVE.
- kernel-devel-azure as component of SUSE Linux Enterprise Server 16.0
- kernel-source-azure as component of SUSE Linux Enterprise Server 16.0
- SUSE Linux Micro Extras 6.2:kernel-obs-build
- SUSE Linux Micro Extras 6.2:kernel-syms
- SLES 15 SP1 CHOST Images for Amazon EC2
- SLES 15 SP2 CHOST Images for Amazon EC2
- SLES 15 SP3 CHOST Images for Amazon EC2
- SLES 15 SP4 CHOST Images for Amazon EC2
- SLES 15 SP5 CHOST Images for Amazon EC2
- SLES 15 SP1 CHOST Images for Google
- SLES 15 SP2 CHOST Images for Google
- SLES 15 SP3 CHOST Images for Google
- Summary
- In the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-39682 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: tls: fix handling of zero-length records on the rx_list
The vendor explicitly identifies these products or versions as containing the fix.
- kernel-64k-debug-debuginfo-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-64k-debug-devel-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-64k-debug-devel-matched-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-64k-debuginfo-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-64k-devel-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-64k-devel-matched-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-debug-debuginfo-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-debug-debuginfo-0:6.12.0-55.37.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-debug-debuginfo-0:6.12.0-55.37.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-debug-debuginfo-0:6.12.0-55.37.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-debug-devel-0:6.12.0-55.37.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
- kernel-debug-devel-0:6.12.0-55.37.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
- Summary
- In the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC CN 4100
- Summary
- In the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.
- Remediation
- Update to V5.0 or later version
CISA confirms exploitation in the wild and lists 2026-09-21 as the remediation due date. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Linux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
What
Linux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
Why
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Linux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
Why
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-09-18.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Check for Unusual or Exceptional Conditions → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-754 ↗
CWE-754: Improper Check for Unusual or Exceptional Conditions. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- kernel-devel-azure as component of SUSE Linux Enterprise Server 16.0
- kernel-source-azure as component of SUSE Linux Enterprise Server 16.0
- SUSE Linux Micro Extras 6.2:kernel-obs-build
- SUSE Linux Micro Extras 6.2:kernel-syms
- SLES 15 SP1 CHOST Images for Amazon EC2
- SLES 15 SP2 CHOST Images for Amazon EC2
- SLES 15 SP3 CHOST Images for Amazon EC2
- SLES 15 SP4 CHOST Images for Amazon EC2
- SLES 15 SP5 CHOST Images for Amazon EC2
- SLES 15 SP1 CHOST Images for Google
- SLES 15 SP2 CHOST Images for Google
- SLES 15 SP3 CHOST Images for Google
- SLES 15 SP4 CHOST Images for Google
- SLES 15 SP5 CHOST Images for Google
- SLES 15 SP1 CHOST Images for Microsoft Azure
- SLES 15 SP2 CHOST Images for Microsoft Azure
- SLES 15 SP3 CHOST Images for Microsoft Azure
- SLES 15 SP4 CHOST Images for Microsoft Azure
- SLES 15 SP5 CHOST Images for Microsoft Azure
- kernel-source-azure as component of openSUSE Leap 16.0
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 5 Sept 2025 · Last source change 7 Oct 2026, 17:56 UTC · CWE-754 · Improper Check for Unusual or Exceptional Conditions
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-31542
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- BlackTree coverageBlackTree article coverage changed from 1 BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- 1 BlackTree article
- After
- 1 BlackTree article
- Affected versionsThe structured affected or fixed version information changed.SUSE Product Security Team ↗
- Before
- kernel-devel-azure as component of SUSE Linux Enterprise Server 16.0; kernel-source-azure as component of SUSE Linux Enterprise Server 16.0; SLES 15 SP1 CHOST Images for Amazon EC2; SLES 15 SP2 CHOST Images for Amazon EC2; SLES 15 SP3 CHOST Images for Amazon EC2; SLES 15 SP4 CHOST Images for Amazon EC2; SLES 15 SP5 CHOST Images for Amazon EC2; SLES 15 SP1 CHOST Images for Google; SLES 15 SP2 CHOST Images for Google; SLES 15 SP3 CHOST Images for Google; SLES 15 SP4 CHOST Images for Google; SLES 15 SP5 CHOST Images for Google; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure; kernel-source-azure as component of openSUSE Leap 16.0 · Fixed: kernel-obs-build-6.12.0-160000.6.1 as component of SUSE Linux Micro Extras 6.2; kernel-syms-6.12.0-160000.6.1 as component of SUSE Linux Micro Extras 6.2
- After
- kernel-devel-azure as component of SUSE Linux Enterprise Server 16.0; kernel-source-azure as component of SUSE Linux Enterprise Server 16.0; SUSE Linux Micro Extras 6.2:kernel-obs-build; SUSE Linux Micro Extras 6.2:kernel-syms; SLES 15 SP1 CHOST Images for Amazon EC2; SLES 15 SP2 CHOST Images for Amazon EC2; SLES 15 SP3 CHOST Images for Amazon EC2; SLES 15 SP4 CHOST Images for Amazon EC2; SLES 15 SP5 CHOST Images for Amazon EC2; SLES 15 SP1 CHOST Images for Google; SLES 15 SP2 CHOST Images for Google; SLES 15 SP3 CHOST Images for Google; SLES 15 SP4 CHOST Images for Google; SLES 15 SP5 CHOST Images for Google; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure; kernel-source-azure as component of openSUSE Leap 16.0
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.ENISA EUVD ↗
- Before
- not listed in ENISA EUVD known-exploited dataset
- After
- listed in ENISA EUVD known-exploited dataset (EUVD-2025-31542)
- CISA KEV stateCISA KEV now confirms exploitation in the wild.CISA KEV ↗
- Before
- not listed in CISA KEV
- After
- listed in CISA KEV since 2026-09-18
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 2902c3ebcca52ca845c03182000e8d71d3a5196f; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 3439c15ae91a517cf3c650ea15a8987699416ad9; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 62708b9452f8eb77513115b17c4f8d1a22ebf843; 6.0 · Fixed: < 6.0; 6.1.149 ≤ 6.1.*; 6.6.103 ≤ 6.6.*; 6.12.44 ≤ 6.12.*; 6.16.4 ≤ 6.16.*; 6.17 ≤ *
- After
- Linux: 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 2902c3ebcca52ca845c03182000e8d71d3a5196f, 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677, 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 3439c15ae91a517cf3c650ea15a8987699416ad9, 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e, 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 62708b9452f8eb77513115b17c4f8d1a22ebf843, 6.0 · Fixed: Linux: < 6.0, 6.1.149 ≤ 6.1.*, 6.6.103 ≤ 6.6.*, 6.12.44 ≤ 6.12.*, 6.16.4 ≤ 6.16.*, 6.17 ≤ *
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.