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

Bluetooth: virtio_bt: validate rx pkt_type header length

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 14 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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: No default targetRemediation target: Normal maintenance

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.

24 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.88-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 5 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-46186 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-46186
151 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: validate rx pkt_type header length virtbt_rx_handle() reads the leading pkt_type byte from the RX skb and forwards the remainder to hci_recv_frame() for every event/ACL/SCO/ISO type, without checking that the remaining payload is at least the fixed HCI header for that type. After the preceding patch bounds the backend-supplied used.len to [1, VIRTBT_RX_BUF_SIZE], a one-byte completion still reaches hci_recv_frame() with skb->len already pulled to 0. If the byte happened to be HCI_ACLDATA_PKT, the ACL-vs-ISO classification fast-path in hci_dev_classify_pkt_type() dereferences hci_acl_hdr(skb)->handle whenever the HCI device has an active CIS_LINK, BIS_LINK, or PA_LINK connection, reading two bytes of uninitialized RX-buffer data. The same hazard exists for every packet type the driver accepts because none of the switch cases in virtbt_rx_handle() check skb->len against the per-type minimum HCI header size before handing the frame to the core. After stripping pkt_type, require skb->len to cover the fixed header size for the selected type (event 2, ACL 4, SCO 3, ISO 4) before calling hci_recv_frame(); drop ratelimited otherwise. Unknown pkt_type values still take the original kfree_skb() default path. Use bt_dev_err_ratelimited() because both the length and pkt_type values come from an untrusted backend that can otherwise flood the kernel log.
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-32813

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: virtio_bt: validate rx pkt_type header length virtbt_rx_handle() reads the leading pkt_type byte from the RX skb and forwards the remainder to hci_recv_frame() for every event/ACL/SCO/ISO type, without checking that the remaining payload is at least the fixed HCI header for that type. After the preceding patch bounds the backend-supplied used.len to [1, VIRTBT_RX_BUF_SIZE], a one-byte completion still reaches hci_recv_frame() with skb->len already pulled to 0. If the byte happened to be HCI_ACLDATA_PKT, the ACL-vs-ISO classification fast-path in hci_dev_classify_pkt_type() dereferences hci_acl_hdr(skb)->handle whenever the HCI device has an active CIS_LINK, BIS_LINK, or PA_LINK connection, reading two bytes of uninitialized RX-buffer data. The same hazard exists for every packet type the driver accepts because none of the switch cases in virtbt_rx_handle() check skb->len against the per-type minimum HCI header size before handing the frame to the core. After stripping pkt_type, require skb->len to cover the fixed header size for the selected type (event 2, ACL 4, SCO 3, ISO 4) before calling hci_recv_frame(); drop ratelimited otherwise. Unknown pkt_type values still take the original kfree_skb() default path. Use bt_dev_err_ratelimited() because both the length and pkt_type values come from an untrusted backend that can otherwise flood the kernel log.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: validate rx pkt_type header length virtbt_rx_handle() reads the leading pkt_type byte from the RX skb and forwards the remainder to hci_recv_frame() for every event/ACL/SCO/ISO type, without checking that the remaining payload is at least the fixed HCI header for that type. After the preceding patch bounds the backend-supplied used.len to [1, VIRTBT_RX_BUF_SIZE], a one-byte completion still reaches hci_recv_frame() with skb->len already pulled to 0. If the byte happened to be HCI_ACLDATA_PKT, the ACL-vs-ISO classification fast-path in hci_dev_classify_pkt_type() dereferences hci_acl_hdr(skb)->handle whenever the HCI device has an active CIS_LINK, BIS_LINK, or PA_LINK connection, reading two bytes of uninitialized RX-buffer data. The same hazard exists for every packet type the driver accepts because none of the switch cases in virtbt_rx_handle() check skb->len against the per-type minimum HCI header size before handing the frame to the core. After stripping pkt_type, require skb->len to cover the fixed header size for the selected type (event 2, ACL 4, SCO 3, ISO 4) before calling hci_recv_frame(); drop ratelimited otherwise. Unknown pkt_type values still take the original kfree_skb() default path. Use bt_dev_err_ratelimited() because both the length and pkt_type values come from an untrusted backend that can otherwise flood the kernel log.

Why

The product uses or accesses a resource that has not been initialized.

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: Bluetooth: virtio_bt: validate rx pkt_type header length virtbt_rx_handle() reads the leading pkt_type byte from the RX skb and forwards the remainder to hci_recv_frame() for every event/ACL/SCO/ISO type, without checking that the remaining payload is at least the fixed HCI header for that type. After the preceding patch bounds the backend-supplied used.len to [1, VIRTBT_RX_BUF_SIZE], a one-byte completion still reaches hci_recv_frame() with skb->len already pulled to 0. If the byte happened to be HCI_ACLDATA_PKT, the ACL-vs-ISO classification fast-path in hci_dev_classify_pkt_type() dereferences hci_acl_hdr(skb)->handle whenever the HCI device has an active CIS_LINK, BIS_LINK, or PA_LINK connection, reading two bytes of uninitialized RX-buffer data. The same hazard exists for every packet type the driver accepts because none of the switch cases in virtbt_rx_handle() check skb->len against the per-type minimum HCI header size before handing the frame to the core. After stripping pkt_type, require skb->len to cover the fixed header size for the selected type (event 2, ACL 4, SCO 3, ISO 4) before calling hci_recv_frame(); drop ratelimited otherwise. Unknown pkt_type values still take the original kfree_skb() default path. Use bt_dev_err_ratelimited() because both the length and pkt_type values come from an untrusted backend that can otherwise flood the kernel log.

Why

The product uses or accesses a resource that has not been initialized.

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 → Use of Uninitialized Resource → 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: a standard category for the underlying weakness.
CWE-908 ↗

CWE-908: Use of Uninitialized Resource. The product uses or accesses a resource that has not been initialized.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-908
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 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-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46182 https://www.cve.org/CVERecord?id=CVE-2026-46182 Référence CVE CVE-2026-46183 https://www.cve.org/CVERecord?id=CVE-2026-46183 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 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-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46182 https://www.cve.org/CVERecord?id=CVE-2026-46182 Référence CVE CVE-2026-46183 https://www.cve.org/CVERecord?id=CVE-2026-46183 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 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-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46182 https://www.cve.org/CVERecord?id=CVE-2026-46182 Référence CVE CVE-2026-46183 https://www.cve.org/CVERecord?id=CVE-2026-46183 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46163 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46209 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-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46182 https://www.cve.org/CVERecord?id=CVE-2026-46182 Référence CVE CVE-2026-46183 https://www.cve.org/CVERecord?id=CVE-2026-46183 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46161 Référence CVE CVE-2026-46163 https://www.cve.org/CVERecord?id=CVE-2026-46163 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46212 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-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46182 https://www.cve.org/CVERecord?id=CVE-2026-46182 Référence CVE CVE-2026-46183 https://www.cve.org/CVERecord?id=CVE-2026-46183 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46194 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46201 https://www.cve.org/CVERecord?id=CVE-2026-46201 Référence CVE CVE-2026-46204 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-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46182 https://www.cve.org/CVERecord?id=CVE-2026-46182 Référence CVE CVE-2026-46183 https://www.cve.org/CVERecord?id=CVE-2026-46183 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46188 https://www.cve.org/CVERecord?id=CVE-2026-46188 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46192 https://www.cve.org/CVERecord?id=CVE-2026-46192 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46194 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46169 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=CVE-2026-46190 Référence CVE CVE-2026-46191 https://www.cve.org/CVERecord?id=CVE-2026-46191 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46196 https://www.cve.org/CVERecord?id=CVE-2026-46196 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0731Multiples vulnérabilités dans les produits Microsoft

mai 2026 Bulletin de sécurité Microsoft CVE-2026-46165 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46167 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46168 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46172 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46173 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46176 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46177 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46178 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46180 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46185 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46186 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46187 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46189 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46190 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46191 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46193 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46195 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46196 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46197 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46198 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46199 du 29 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019506LinuxのLinux Kernelにおける初期化されていないリソースの使用に関する脆弱性

Linuxカーネルにおいて、Bluetoothのvirtio_btドライバーでrx pkt_typeヘッダー長の検証に関する脆弱性が修正されました。virtbt_rx_handle()関数は受信したskbから先頭のpkt_typeバイトを読み取り、残りのデータをすべてのevent/ACL/SCO/ISOタイプに対してhci_recv_frame()に渡しますが、残りのペイロードがタイプごとの固定HCIヘッダーサイズ以上であるかを確認していませんでした。特にACLデータパケットの処理時に初期化されていないバッファデータを読み取る可能性があり、不正なメモリ参照が起こる恐れがありました。本脆弱性はパケット長とpkt_type情報が信頼できない場合に発生し得るもので、対応としてpkt_typeに応じた最低限のヘッダー長を検証し、不足する場合はログを制限しつつパケットを破棄するように修正されました。これにより、不正なパケットによるカーネルのメモリ破壊や予期せぬ動作を防止します。

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.1, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 7.0.*, 7.1 ≤ *
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 28 May 2026 · Last source change 14 Jun 2026, 18:01 UTC · CWE-908 · Use of Uninitialized Resource

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

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-32813↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update 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-46186 · cve.blacktree.nl