BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-74551High confidence

hwmon: (nzxt-smart2) DMA-align output buffer

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

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 product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 17 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

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.

Distribution package intelligence

Release-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.

25 package states
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 releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.105-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.107-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative 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.

1 current
CVE-2026-74551 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: hwmon: (nzxt-smart2) DMA-align output buffer
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's `hwmon: (nzxt-smart2)` driver. This vulnerability allows for immediate and deterministic memory corruption on systems with non-coherent CPU architectures, such as ARM or MIPS. When operations like setting a fan speed or updating an interval trigger a USB Direct Memory Access (DMA) mapping, the DMA process can corrupt adjacent variables due to cacheline sharing. This issue is resolved by aligning the output buffer to prevent unintended data corruption.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-59616

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: hwmon: (nzxt-smart2) DMA-align output buffer Sashiko reports: When send_output_report() calls hid_hw_output_report(), the underlying USB HID core calls usb_interrupt_msg() which maps this buffer directly for DMA. When the DMA mapping flushes or invalidates the cacheline, it will corrupt the adjacent variables (mutex, update_interval) that were modified concurrently by the CPU. This causes memory corruption due to cacheline sharing on non-coherent CPU architectures (such as ARM or MIPS). The DMA API debugging tool (CONFIG_DMA_API_DEBUG) will trigger runtime warnings for this violation. Any operation that triggers send_output_report() (like setting a fan speed or updating the interval) causes the USB DMA mapping. On systems with non-coherent caches, this structural bug causes immediate and deterministic memory corruption. Align the output buffer to ARCH_DMA_MINALIGN to fix the problem.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

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 product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: hwmon: (nzxt-smart2) DMA-align output buffer Sashiko reports: When send_output_report() calls hid_hw_output_report(), the underlying USB HID core calls usb_interrupt_msg() which maps this buffer directly for DMA. When the DMA mapping flushes or invalidates the cacheline, it will corrupt the adjacent variables (mutex, update_interval) that were modified concurrently by the CPU. This causes memory corruption due to cacheline sharing on non-coherent CPU architectures (such as ARM or MIPS). The DMA API debugging tool (CONFIG_DMA_API_DEBUG) will trigger runtime warnings for this violation. Any operation that triggers send_output_report() (like setting a fan speed or updating the interval) causes the USB DMA mapping. On systems with non-coherent caches, this structural bug causes immediate and deterministic memory corruption. Align the output buffer to ARCH_DMA_MINALIGN to fix the problem.

What

In the Linux kernel, the following vulnerability has been resolved: hwmon: (nzxt-smart2) DMA-align output buffer Sashiko reports: When send_output_report() calls hid_hw_output_report(), the underlying USB HID core calls usb_interrupt_msg() which maps this buffer directly for DMA. When the DMA mapping flushes or invalidates the cacheline, it will corrupt the adjacent variables (mutex, update_interval) that were modified concurrently by the CPU. This causes memory corruption due to cacheline sharing on non-coherent CPU architectures (such as ARM or MIPS). The DMA API debugging tool (CONFIG_DMA_API_DEBUG) will trigger runtime warnings for this violation. Any operation that triggers send_output_report() (like setting a fan speed or updating the interval) causes the USB DMA mapping. On systems with non-coherent caches, this structural bug causes immediate and deterministic memory corruption. Align the output buffer to ARCH_DMA_MINALIGN to fix the problem.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. 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: hwmon: (nzxt-smart2) DMA-align output buffer Sashiko reports: When send_output_report() calls hid_hw_output_report(), the underlying USB HID core calls usb_interrupt_msg() which maps this buffer directly for DMA. When the DMA mapping flushes or invalidates the cacheline, it will corrupt the adjacent variables (mutex, update_interval) that were modified concurrently by the CPU. This causes memory corruption due to cacheline sharing on non-coherent CPU architectures (such as ARM or MIPS). The DMA API debugging tool (CONFIG_DMA_API_DEBUG) will trigger runtime warnings for this violation. Any operation that triggers send_output_report() (like setting a fan speed or updating the interval) causes the USB DMA mapping. On systems with non-coherent caches, this structural bug causes immediate and deterministic memory corruption. Align the output buffer to ARCH_DMA_MINALIGN to fix the problem.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. 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 exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

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
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

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
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level 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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-59616Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: hwmon: (nzxt-smart2) DMA-align output buffer Sashiko reports: When send_output_report() calls hid_hw_output_report(), the underlying USB HID core calls usb_interrupt_msg() which maps this buffer directly for DMA. When the DMA mapping flushes or invalidates the cacheline, it will corrupt the adjacent variables (mutex, update_interval) that were modified concurrently by the CPU. This causes memory corruption due to cacheline sharing on non-coherent CPU architectures (such as ARM or MIPS). The DMA API debugging tool (CONFIG_DMA_API_DEBUG) will trigger runtime warnings for this violation. Any operation that triggers send_output_report() (like setting a fan speed or updating the interval) causes the USB DMA mapping. On systems with non-coherent caches, this structural bug causes immediate and deterministic memory corruption. Align the output buffer to ARCH_DMA_MINALIGN to fix the problem.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1232Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-74540 Référence CVE CVE-2026-74541 https://www.cve.org/CVERecord?id=CVE-2026-74541 Référence CVE CVE-2026-74543 https://www.cve.org/CVERecord?id=CVE-2026-74543 Référence CVE CVE-2026-74545 https://www.cve.org/CVERecord?id=CVE-2026-74545 Référence CVE CVE-2026-74546 https://www.cve.org/CVERecord?id=CVE-2026-74546 Référence CVE CVE-2026-74547 https://www.cve.org/CVERecord?id=CVE-2026-74547 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74549 https://www.cve.org/CVERecord?id=CVE-2026-74549 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74551 https://www.cve.org/CVERecord?id=CVE-2026-74551 Référence CVE CVE-2026-74552 https://www.cve.org/CVERecord?id=CVE-2026-74552 Référence CVE CVE-2026-74553 https://www.cve.org/CVERecord?id=CVE-2026-74553 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74564 https://www.cve.org/CVERecord?id=CVE-2026-74564 Référence CVE CVE-2026-74565 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1163Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-74522 Référence CVE CVE-2026-74523 https://www.cve.org/CVERecord?id=CVE-2026-74523 Référence CVE CVE-2026-74525 https://www.cve.org/CVERecord?id=CVE-2026-74525 Référence CVE CVE-2026-74540 https://www.cve.org/CVERecord?id=CVE-2026-74540 Référence CVE CVE-2026-74546 https://www.cve.org/CVERecord?id=CVE-2026-74546 Référence CVE CVE-2026-74547 https://www.cve.org/CVERecord?id=CVE-2026-74547 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74549 https://www.cve.org/CVERecord?id=CVE-2026-74549 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74551 https://www.cve.org/CVERecord?id=CVE-2026-74551 Référence CVE CVE-2026-74552 https://www.cve.org/CVERecord?id=CVE-2026-74552 Référence CVE CVE-2026-74553 https://www.cve.org/CVERecord?id=CVE-2026-74553 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74564 https://www.cve.org/CVERecord?id=CVE-2026-74564 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1090Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-74540 Référence CVE CVE-2026-74541 https://www.cve.org/CVERecord?id=CVE-2026-74541 Référence CVE CVE-2026-74543 https://www.cve.org/CVERecord?id=CVE-2026-74543 Référence CVE CVE-2026-74545 https://www.cve.org/CVERecord?id=CVE-2026-74545 Référence CVE CVE-2026-74546 https://www.cve.org/CVERecord?id=CVE-2026-74546 Référence CVE CVE-2026-74547 https://www.cve.org/CVERecord?id=CVE-2026-74547 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74549 https://www.cve.org/CVERecord?id=CVE-2026-74549 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74551 https://www.cve.org/CVERecord?id=CVE-2026-74551 Référence CVE CVE-2026-74552 https://www.cve.org/CVERecord?id=CVE-2026-74552 Référence CVE CVE-2026-74553 https://www.cve.org/CVERecord?id=CVE-2026-74553 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74564 https://www.cve.org/CVERecord?id=CVE-2026-74564 Référence CVE CVE-2026-74565 https://www.cve.org/CVERecord?id=

Official advisory ↗
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
Linux: 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 81a6593b1c8dfb2694cd0ce39be01212d2b8436c, 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 70ad543ce81f368411b6c721265a3b2d7ab4fda4, 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f, 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 2332d35aaf206c17acf848522817252732596676, 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa, 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8, 5.17
Fixed
Linux: < 5.17, 6.1.183 ≤ 6.1.*, 6.6.151 ≤ 6.6.*, 6.12.103 ≤ 6.12.*, 6.18.44 ≤ 6.18.*, 7.1.8 ≤ 7.1.*, 7.2 ≤ *
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Aug 2026 · Last source change 19 Aug 2026, 16:38 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-59616
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/81a6593b1c8dfb2694cd0ce39be01212d2b8436c; removed remediation: git.kernel.org/70ad543ce81f368411b6c721265a3b2d7ab4fda4.
    Before
    remediation: git.kernel.org/70ad543ce81f368411b6c721265a3b2d7ab4fda4
    After
    remediation: git.kernel.org/81a6593b1c8dfb2694cd0ce39be01212d2b8436c
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    53e68c20aeb1e23419bed811aa3a309ceda200f9 < 70ad543ce81f368411b6c721265a3b2d7ab4fda4; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 2332d35aaf206c17acf848522817252732596676; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8; 5.17 · Fixed: < 5.17; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    53e68c20aeb1e23419bed811aa3a309ceda200f9 < 81a6593b1c8dfb2694cd0ce39be01212d2b8436c; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 70ad543ce81f368411b6c721265a3b2d7ab4fda4; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 2332d35aaf206c17acf848522817252732596676; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8; 5.17 · Fixed: < 5.17; 6.1.183 ≤ 6.1.*; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    53e68c20aeb1e23419bed811aa3a309ceda200f9 < 70ad543ce81f368411b6c721265a3b2d7ab4fda4; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 2332d35aaf206c17acf848522817252732596676; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8; 5.17 · Fixed: < 5.17; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2-rc6 ≤ *
    After
    53e68c20aeb1e23419bed811aa3a309ceda200f9 < 70ad543ce81f368411b6c721265a3b2d7ab4fda4; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 2332d35aaf206c17acf848522817252732596676; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa; 53e68c20aeb1e23419bed811aa3a309ceda200f9 < 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8; 5.17 · Fixed: < 5.17; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  5. CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    7.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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.
Free version - for non-commercial use only.CVE-2026-74551 · cve.blacktree.nl