Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.54% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-31467High confidence
erofs: add GFP_NOIO in the bio completion if needed
Linux · Linux
7.5HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 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 severityHigh→Operational priority:High, 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.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Linux Linux 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- 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.85-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.1.170-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.19.11-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.19.11-1 | Debian Security Tracker ↗Source updated 5 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 5 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 5 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 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-fde | 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 Oct 2026 |
Direct vendor intelligence
2 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-2026-31467 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Linux kernel: Denial of Service in erofs filesystem
The vendor explicitly identifies these products or versions as containing the fix.
- kernel-64k-debug-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-debug-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-debug-devel-matched-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-devel-matched-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- Summary
- A flaw was found in the Linux kernel's erofs filesystem. A remote attacker can exploit this vulnerability without requiring any privileges. This issue occurs when insufficient memory during a memory mapping operation (vm_map_ram()) in the bio completion path leads to a deadlock, causing a Denial of Service (DoS).
- 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. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
CVE-2026-31467 · CSAF 2.0 · revision 8 · interimSUSE Product Security TeamCVE-2026-31467
The vendor explicitly identifies these products as affected by this CVE.
- kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
- kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
- kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
- kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
- kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
- kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
- cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
- dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
- gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
- kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
- kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
- ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
- Summary
- In the Linux kernel, the following vulnerability has been resolved: erofs: add GFP_NOIO in the bio completion if needed The bio completion path in the process context (e.g. dm-verity) will directly call into decompression rather than trigger another workqueue context for minimal scheduling latencies, which can then call vm_map_ram() with GFP_KERNEL. Due to insufficient memory, vm_map_ram() may generate memory swapping I/O, which can cause submit_bio_wait to deadlock in some scenarios. Trimmed down the call stack, as follows: f2fs_submit_read_io submit_bio //bio_list is initialized. mmc_blk_mq_recovery z_erofs_endio vm_map_ram __pte_alloc_kernel __alloc_pages_direct_reclaim shrink_folio_list __swap_writepage submit_bio_wait //bio_list is non-NULL, hang!!! Use memalloc_noio_{save,restore}() to wrap up this path.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 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
In the Linux kernel, the following vulnerability has been resolved: erofs: add GFP_NOIO in the bio completion if needed The bio completion path in the process context (e.g. dm-verity) will directly call into decompression rather than trigger another workqueue context for minimal scheduling latencies, which can then call vm_map_ram() with GFP_KERNEL. Due to insufficient memory, vm_map_ram() may generate memory swapping I/O, which can cause submit_bio_wait to deadlock in some scenarios. Trimmed down the call stack, as follows: f2fs_submit_read_io submit_bio //bio_list is initialized. mmc_blk_mq_recovery z_erofs_endio vm_map_ram __pte_alloc_kernel __alloc_pages_direct_reclaim shrink_folio_list __swap_writepage submit_bio_wait //bio_list is non-NULL, hang!!! Use memalloc_noio_{save,restore}() to wrap up this path.
What
In the Linux kernel, the following vulnerability has been resolved: erofs: add GFP_NOIO in the bio completion if needed The bio completion path in the process context (e.g. dm-verity) will directly call into decompression rather than trigger another workqueue context for minimal scheduling latencies, which can then call vm_map_ram() with GFP_KERNEL. Due to insufficient memory, vm_map_ram() may generate memory swapping I/O, which can cause submit_bio_wait to deadlock in some scenarios. Trimmed down the call stack, as follows: f2fs_submit_read_io submit_bio //bio_list is initialized. mmc_blk_mq_recovery z_erofs_endio vm_map_ram __pte_alloc_kernel __alloc_pages_direct_reclaim shrink_folio_list __swap_writepage submit_bio_wait //bio_list is non-NULL, hang!!! Use memalloc_noio_{save,restore}() to wrap up this path.
Why
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
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
In the Linux kernel, the following vulnerability has been resolved: erofs: add GFP_NOIO in the bio completion if needed The bio completion path in the process context (e.g. dm-verity) will directly call into decompression rather than trigger another workqueue context for minimal scheduling latencies, which can then call vm_map_ram() with GFP_KERNEL. Due to insufficient memory, vm_map_ram() may generate memory swapping I/O, which can cause submit_bio_wait to deadlock in some scenarios. Trimmed down the call stack, as follows: f2fs_submit_read_io submit_bio //bio_list is initialized. mmc_blk_mq_recovery z_erofs_endio vm_map_ram __pte_alloc_kernel __alloc_pages_direct_reclaim shrink_folio_list __swap_writepage submit_bio_wait //bio_list is non-NULL, hang!!! Use memalloc_noio_{save,restore}() to wrap up this path.
Why
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
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 Locking → 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-667 ↗
CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
- 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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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
- Fixed
- kernel-64k-debug-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-debug-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-debug-devel-matched-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-64k-devel-matched-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-debuginfo-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-matched-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-matched-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-matched-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debug-devel-matched-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-common-aarch64-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-common-ppc64le-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-common-s390x-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-debuginfo-common-x86_64-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-devel-0:6.12.0-55.108.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-devel-0:6.12.0-55.108.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-devel-0:6.12.0-55.108.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- kernel-devel-0:6.12.0-55.108.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- and 586 more
- 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 22 Apr 2026 · Last source change 5 Aug 2026, 12:22 UTC · CWE-667 · Improper Locking
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-2026-24814
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
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
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
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.