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

Bluetooth: qca: fix NVM tag length underflow in TLV parser

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

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: Manual assessmentRemediation target: Manual assessment

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.101-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.101-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.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 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-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 5 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 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
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 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-64573 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-64573
182 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-53267

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. 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: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

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 the affected interface may attempt exploitation when the stated preconditions are met. 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: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

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 the affected interface may attempt exploitation when the stated preconditions are met. 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-53267Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um den Speicher zu beschädigen, einen Denial-of-Service-Zustand auszulösen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

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

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

d?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 https://www.cve.org/CVERecord?id=CVE-2026-64565 Référence CVE CVE-2026-64567 https://www.cve.org/CVERecord?id=CVE-2026-64567 Référence CVE CVE-2026-64568 https://www.cve.org/CVERecord?id=CVE-2026-64568 Référence CVE CVE-2026-64569 https://www.cve.org/CVERecord?id=CVE-2026-64569 Référence CVE CVE-2026-64570 https://www.cve.org/CVERecord?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 https://www.cve.org/CVERecord?id=CVE-2026-64565 Référence CVE CVE-2026-64567 https://www.cve.org/CVERecord?id=CVE-2026-64567 Référence CVE CVE-2026-64568 https://www.cve.org/CVERecord?id=CVE-2026-64568 Référence CVE CVE-2026-64569 https://www.cve.org/CVERecord?id=CVE-2026-64569 Référence CVE CVE-2026-64570 https://www.cve.org/CVERecord?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-64585 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-64561 Référence CVE CVE-2026-64562 https://www.cve.org/CVERecord?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 https://www.cve.org/CVERecord?id=CVE-2026-64565 Référence CVE CVE-2026-64567 https://www.cve.org/CVERecord?id=CVE-2026-64567 Référence CVE CVE-2026-64569 https://www.cve.org/CVERecord?id=CVE-2026-64569 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64578 https://www.cve.org/CVERecord?id=CVE-2026-64578 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64580 https://www.cve.org/CVERecord?id=CVE-2026-64580 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64565 https://www.cve.org/CVERecord?id=CVE-2026-64565 Référence CVE CVE-2026-64567 https://www.cve.org/CVERecord?id=CVE-2026-64567 Référence CVE CVE-2026-64568 https://www.cve.org/CVERecord?id=CVE-2026-64568 Référence CVE CVE-2026-64569 https://www.cve.org/CVERecord?id=CVE-2026-64569 Référence CVE CVE-2026-64570 https://www.cve.org/CVERecord?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-64585 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 https://www.cve.org/CVERecord?id=CVE-2026-64565 Référence CVE CVE-2026-64567 https://www.cve.org/CVERecord?id=CVE-2026-64567 Référence CVE CVE-2026-64568 https://www.cve.org/CVERecord?id=CVE-2026-64568 Référence CVE CVE-2026-64569 https://www.cve.org/CVERecord?id=CVE-2026-64569 Référence CVE CVE-2026-64570 https://www.cve.org/CVERecord?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64578 https://www.cve.org/CVERecord?id=CVE-2026-64578 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64580 https://www.cve.org/CVERecord?id=CVE-2026-64580 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 https://www.cve.org/CVERecord?id=CVE-2026-64565 Référence CVE CVE-2026-64567 https://www.cve.org/CVERecord?id=CVE-2026-64567 Référence CVE CVE-2026-64568 https://www.cve.org/CVERecord?id=CVE-2026-64568 Référence CVE CVE-2026-64569 https://www.cve.org/CVERecord?id=CVE-2026-64569 Référence CVE CVE-2026-64570 https://www.cve.org/CVERecord?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64578 https://www.cve.org/CVERecord?id=CVE-2026-64578 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64580 https://www.cve.org/CVERecord?id=CVE-2026-64580 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 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
Fixed
Linux: < 6.9, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.1.6 ≤ 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 5 Aug 2026 · Last source change 19 Aug 2026, 16:28 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-53267
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CVSS base score, 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/a7ee11441d71ab036a705d110a415421f5a4a898; removed remediation: git.kernel.org/70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24.
    Before
    remediation: git.kernel.org/70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24
    After
    remediation: git.kernel.org/a7ee11441d71ab036a705d110a415421f5a4a898
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    427281f9498ed614f9aabc80e46ec077c487da6d < 70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 59fd2f075bca94f030c7c78e94878ea0803d7690; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < a087ed960fce54e9302796229e9d545bbc9bcd4a; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 4fcfb5b2c736785464ff9745f94c6726c5ee2d85; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < c90164ca0f7036942ba088eb7ea8d3f6c2352020; ed53949cc92e28aaa3463d246942bda1fbb7f307; 1caceadfb50432dbf6d808796cb6c34ebb6d662c; 02f05ed44b71152d5e11d29be28aed91c0489b4e · Fixed: < 6.9; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    ed53949cc92e28aaa3463d246942bda1fbb7f307 < a7ee11441d71ab036a705d110a415421f5a4a898; 1caceadfb50432dbf6d808796cb6c34ebb6d662c < 5d34e537755d2f9eba2d4e54d70126f987ef20b4; 427281f9498ed614f9aabc80e46ec077c487da6d < 70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 59fd2f075bca94f030c7c78e94878ea0803d7690; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < a087ed960fce54e9302796229e9d545bbc9bcd4a; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 4fcfb5b2c736785464ff9745f94c6726c5ee2d85; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < c90164ca0f7036942ba088eb7ea8d3f6c2352020; 02f05ed44b71152d5e11d29be28aed91c0489b4e · Fixed: < 6.9; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    427281f9498ed614f9aabc80e46ec077c487da6d < 70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 59fd2f075bca94f030c7c78e94878ea0803d7690; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < a087ed960fce54e9302796229e9d545bbc9bcd4a; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 4fcfb5b2c736785464ff9745f94c6726c5ee2d85; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < c90164ca0f7036942ba088eb7ea8d3f6c2352020; ed53949cc92e28aaa3463d246942bda1fbb7f307; 1caceadfb50432dbf6d808796cb6c34ebb6d662c; 02f05ed44b71152d5e11d29be28aed91c0489b4e · Fixed: < 6.9; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc4 ≤ *
    After
    427281f9498ed614f9aabc80e46ec077c487da6d < 70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 59fd2f075bca94f030c7c78e94878ea0803d7690; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < a087ed960fce54e9302796229e9d545bbc9bcd4a; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < 4fcfb5b2c736785464ff9745f94c6726c5ee2d85; 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d < c90164ca0f7036942ba088eb7ea8d3f6c2352020; ed53949cc92e28aaa3463d246942bda1fbb7f307; 1caceadfb50432dbf6d808796cb6c34ebb6d662c; 02f05ed44b71152d5e11d29be28aed91c0489b4e · Fixed: < 6.9; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-53267↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-64573 · cve.blacktree.nl