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

wifi: iwlwifi: mvm: fix driver-set TX rates on old devices

Linux · Linux

8.1HighCVSS 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 13 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.21% 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: Within 30 daysRemediation target: Within 180 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 13 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.

17 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 13 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-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 5 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, 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 5 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 5 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 5 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 5 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-64176 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: wifi: iwlwifi: mvm: fix driver-set TX rates on old devices
98 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the Linux kernel's iwlwifi driver, affecting older Intel wireless devices. This vulnerability arises from incorrect handling of transmit (TX) rates, specifically when the driver attempts to set these rates. An attacker could potentially trigger a firmware assert or crash, leading to a denial of service (DoS) for the affected wireless functionality.
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.
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-45861

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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 13 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: wifi: iwlwifi: mvm: fix driver-set TX rates on old devices On old devices such as 7265D, rates are still encoded in version 1 format, which doesn't use the CCK/OFDM rate index (0-3/0-7) but rather their PLCP value (e.g. 10 for 1 Mbps CCK rate.) While introducing v3 rates, I changed the driver from internally handling v1 rates and converting to v2, to internally handling v3 and converting to v1 or v2 according to the firmware. I accordingly changed the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer have different values for different APIs. This was correct. However, I later reverted this part of the change, because it was reported that I had broken beacon rates, causing a FW assert/crash. This caused TX_CMD rates to be set incorrectly, potentially causing a warning when reported back from the device as having been used. Fix this (hopefully correctly now) by handling beacon rates in the TX_CMD that's embedded in the beacon template command separately. Restore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate index, not PLCP value, fixing the real TX_CMD.

What

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix driver-set TX rates on old devices On old devices such as 7265D, rates are still encoded in version 1 format, which doesn't use the CCK/OFDM rate index (0-3/0-7) but rather their PLCP value (e.g. 10 for 1 Mbps CCK rate.) While introducing v3 rates, I changed the driver from internally handling v1 rates and converting to v2, to internally handling v3 and converting to v1 or v2 according to the firmware. I accordingly changed the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer have different values for different APIs. This was correct. However, I later reverted this part of the change, because it was reported that I had broken beacon rates, causing a FW assert/crash. This caused TX_CMD rates to be set incorrectly, potentially causing a warning when reported back from the device as having been used. Fix this (hopefully correctly now) by handling beacon rates in the TX_CMD that's embedded in the beacon template command separately. Restore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate index, not PLCP value, fixing the real TX_CMD.

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 an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix driver-set TX rates on old devices On old devices such as 7265D, rates are still encoded in version 1 format, which doesn't use the CCK/OFDM rate index (0-3/0-7) but rather their PLCP value (e.g. 10 for 1 Mbps CCK rate.) While introducing v3 rates, I changed the driver from internally handling v1 rates and converting to v2, to internally handling v3 and converting to v1 or v2 according to the firmware. I accordingly changed the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer have different values for different APIs. This was correct. However, I later reverted this part of the change, because it was reported that I had broken beacon rates, causing a FW assert/crash. This caused TX_CMD rates to be set incorrectly, potentially causing a warning when reported back from the device as having been used. Fix this (hopefully correctly now) by handling beacon rates in the TX_CMD that's embedded in the beacon template command separately. Restore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate index, not PLCP value, fixing the real TX_CMD.

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 an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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
an adjacent network → vulnerable operation → disrupt the affected service
Attack surface
Adjacent
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.
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:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close 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.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.
UnauthenticatedDenial of service
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64167 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64169 https://www.cve.org/CVERecord?id=CVE-2026-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64171 https://www.cve.org/CVERecord?id=CVE-2026-64171 Référence CVE CVE-2026-64172 https://www.cve.org/CVERecord?id=CVE-2026-64172 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64167 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64169 https://www.cve.org/CVERecord?id=CVE-2026-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64171 https://www.cve.org/CVERecord?id=CVE-2026-64171 Référence CVE CVE-2026-64172 https://www.cve.org/CVERecord?id=CVE-2026-64172 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63919 Référence CVE CVE-2026-63921 https://www.cve.org/CVERecord?id=CVE-2026-63921 Référence CVE CVE-2026-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64387 https://www.cve.org/CVERecord?id=CVE-2026-64387 Référence CVE CVE-2026-64414 https://www.cve.org/CVERecord?id=CVE-2026-64414 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64456 https://www.cve.org/CVERecord?id=CVE-2026-64456 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-68128 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64167 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64169 https://www.cve.org/CVERecord?id=CVE-2026-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64171 https://www.cve.org/CVERecord?id=CVE-2026-64171 Référence CVE CVE-2026-64172 https://www.cve.org/CVERecord?id=CVE-2026-64172 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64167 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64169 https://www.cve.org/CVERecord?id=CVE-2026-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64171 https://www.cve.org/CVERecord?id=CVE-2026-64171 Référence CVE CVE-2026-64172 https://www.cve.org/CVERecord?id=CVE-2026-64172 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64167 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64169 https://www.cve.org/CVERecord?id=CVE-2026-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64171 https://www.cve.org/CVERecord?id=CVE-2026-64171 Référence CVE CVE-2026-64172 https://www.cve.org/CVERecord?id=CVE-2026-64172 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64167 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64169 https://www.cve.org/CVERecord?id=CVE-2026-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64171 https://www.cve.org/CVERecord?id=CVE-2026-64171 Référence CVE CVE-2026-64172 https://www.cve.org/CVERecord?id=CVE-2026-64172 Référence CVE CVE-2026-64173 https://www.cve.org/CVERecord?id=CVE-2026-64173 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64181 https://www.cve.org/CVERecord?id=CVE-2026-64181 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028253LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。wifi: iwlwifi: mvm: 古いデバイスにおけるドライバー設定のTXレートの修正。7265Dのような古いデバイスでは、レートはまだバージョン1形式でエンコードされており、これはCCK/OFDMのレートインデックス（0-3/0-7）を使わずに、そのPLCP値（例：1 MbpsのCCKレートは10）を用いています。v3レートを導入する際に、ドライバーの内部処理をv1レートを扱ってv2に変換する方式から、内部でv3を扱いファームウェアに応じてv1またはv2に変換する方式へ変更しました。それに伴い、iwl_mvm_mac80211_idx_to_hwrate()のコードも異なるAPIで異なる値を返さないように変更し、これは正しい対応でした。しかしその後、一部のユーザーからビーコンレートが破損し、ファームウェアがアサートやクラッシュを起こすという報告を受け、この変更を元に戻しました。この影響でTX_CMDのレート設定が誤り、デバイスから使用された際に警告が発生する可能性がありました。この問題を（おそらく正しく）修正するために、ビーコンテンプレートコマンドに埋め込まれたTX_CMD内のビーコンレートを別途扱うようにしました。また、iwl_mvm_mac80211_idx_to_hwrate()はPLCP値ではなくレートインデックスのみを返すように復元し、実際のTX_CMDを正しく修正しました。

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
Fixed
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 19 Jul 2026 · Last source change 5 Aug 2026, 12:39 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-14
European sourceENISA EUVD · EUVD-2026-45861
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD enriched

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 from remediation: access.redhat.com/CVE-2026-64176 to remediation: access.redhat.com/CVE-2026-64176.
    Before
    remediation: access.redhat.com/CVE-2026-64176
    After
    remediation: access.redhat.com/CVE-2026-64176
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 230 more
    After
    bpftool as a component of Red Hat Enterprise Linux 7; kernel as a component of Red Hat Enterprise Linux 7; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7; kernel-bootwrapper as a component of Red Hat Enterprise Linux 7; kernel-debug as a component of Red Hat Enterprise Linux 7; kernel-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-devel as a component of Red Hat Enterprise Linux 7; kernel-doc as a component of Red Hat Enterprise Linux 7; kernel-headers as a component of Red Hat Enterprise Linux 7; kernel-kdump as a component of Red Hat Enterprise Linux 7; kernel-kdump-devel as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 7; kernel-rt-debug as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-doc as a component of Red Hat Enterprise Linux 7; kernel-rt-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-trace as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt.src as a component of Red Hat Enterprise Linux 7; kernel-tools as a component of Red Hat Enterprise Linux 7; kernel-tools-libs as a component of Red Hat Enterprise Linux 7; kernel-tools-libs-devel as a component of Red Hat Enterprise Linux 7; kernel.src as a component of Red Hat Enterprise Linux 7; perf as a component of Red Hat Enterprise Linux 7; python-perf as a component of Red Hat Enterprise Linux 7; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; and 68 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.56.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 582 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45861↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-64176 · cve.blacktree.nl