BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-46680High confidence

Bluetooth: btnxpuart: Fix random crash seen while removing driver

Linux · Linux

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 14 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.

18 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 14 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.10.9-1Debian 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.6.10.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.9-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-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-oem-6.8Affected, 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-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-2024-46680 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: btnxpuart: Fix random crash seen while removing driver
198 known not affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's Bluetooth `btnxpuart` driver. A local user can exploit this vulnerability by repeatedly loading and unloading the driver. This action can cause a scheduled work item to execute after the driver module has been removed, leading to a kernel crash and a denial of service.
Remediation
No remediation text is recorded.
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-41941

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 14 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: btnxpuart: Fix random crash seen while removing driver This fixes the random kernel crash seen while removing the driver, when running the load/unload test over multiple iterations. 1) modprobe btnxpuart 2) hciconfig hci0 reset 3) hciconfig (check hci0 interface up with valid BD address) 4) modprobe -r btnxpuart Repeat steps 1 to 4 The ps_wakeup() call in btnxpuart_close() schedules the psdata->work(), which gets scheduled after module is removed, causing a kernel crash. This hidden issue got highlighted after enabling Power Save by default in 4183a7be7700 (Bluetooth: btnxpuart: Enable Power Save feature on startup) The new ps_cleanup() deasserts UART break immediately while closing serdev device, cancels any scheduled ps_work and destroys the ps_lock mutex. [ 85.884604] Unable to handle kernel paging request at virtual address ffffd4a61638f258 [ 85.884624] Mem abort info: [ 85.884625] ESR = 0x0000000086000007 [ 85.884628] EC = 0x21: IABT (current EL), IL = 32 bits [ 85.884633] SET = 0, FnV = 0 [ 85.884636] EA = 0, S1PTW = 0 [ 85.884638] FSC = 0x07: level 3 translation fault [ 85.884642] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041dd0000 [ 85.884646] [ffffd4a61638f258] pgd=1000000095fff003, p4d=1000000095fff003, pud=100000004823d003, pmd=100000004823e003, pte=0000000000000000 [ 85.884662] Internal error: Oops: 0000000086000007 [#1] PREEMPT SMP [ 85.890932] Modules linked in: algif_hash algif_skcipher af_alg overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_spdif snd_soc_fsl_micfil snd_soc_fsl_sai snd_soc_fsl_utils gpio_ir_recv rc_core fuse [last unloaded: btnxpuart(O)] [ 85.927297] CPU: 1 PID: 67 Comm: kworker/1:3 Tainted: G O 6.1.36+g937b1be4345a #1 [ 85.936176] Hardware name: FSL i.MX8MM EVK board (DT) [ 85.936182] Workqueue: events 0xffffd4a61638f380 [ 85.936198] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 85.952817] pc : 0xffffd4a61638f258 [ 85.952823] lr : 0xffffd4a61638f258 [ 85.952827] sp : ffff8000084fbd70 [ 85.952829] x29: ffff8000084fbd70 x28: 0000000000000000 x27: 0000000000000000 [ 85.963112] x26: ffffd4a69133f000 x25: ffff4bf1c8540990 x24: ffff4bf215b87305 [ 85.963119] x23: ffff4bf215b87300 x22: ffff4bf1c85409d0 x21: ffff4bf1c8540970 [ 85.977382] x20: 0000000000000000 x19: ffff4bf1c8540880 x18: 0000000000000000 [ 85.977391] x17: 0000000000000000 x16: 0000000000000133 x15: 0000ffffe2217090 [ 85.977399] x14: 0000000000000001 x13: 0000000000000133 x12: 0000000000000139 [ 85.977407] x11: 0000000000000001 x10: 0000000000000a60 x9 : ffff8000084fbc50 [ 85.977417] x8 : ffff4bf215b7d000 x7 : ffff4bf215b83b40 x6 : 00000000000003e8 [ 85.977424] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : 0000000000000000 [ 85.977432] x2 : 0000000000000000 x1 : ffff4bf1c4265880 x0 : 0000000000000000 [ 85.977443] Call trace: [ 85.977446] 0xffffd4a61638f258 [ 85.977451] 0xffffd4a61638f3e8 [ 85.977455] process_one_work+0x1d4/0x330 [ 85.977464] worker_thread+0x6c/0x430 [ 85.977471] kthread+0x108/0x10c [ 85.977476] ret_from_fork+0x10/0x20 [ 85.977488] Code: bad PC value [ 85.977491] ---[ end trace 0000000000000000 ]--- Preset since v6.9.11

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix random crash seen while removing driver This fixes the random kernel crash seen while removing the driver, when running the load/unload test over multiple iterations. 1) modprobe btnxpuart 2) hciconfig hci0 reset 3) hciconfig (check hci0 interface up with valid BD address) 4) modprobe -r btnxpuart Repeat steps 1 to 4 The ps_wakeup() call in btnxpuart_close() schedules the psdata->work(), which gets scheduled after module is removed, causing a kernel crash. This hidden issue got highlighted after enabling Power Save by default in 4183a7be7700 (Bluetooth: btnxpuart: Enable Power Save feature on startup) The new ps_cleanup() deasserts UART break immediately while closing serdev device, cancels any scheduled ps_work and destroys the ps_lock mutex. [ 85.884604] Unable to handle kernel paging request at virtual address ffffd4a61638f258 [ 85.884624] Mem abort info: [ 85.884625] ESR = 0x0000000086000007 [ 85.884628] EC = 0x21: IABT (current EL), IL = 32 bits [ 85.884633] SET = 0, FnV = 0 [ 85.884636] EA = 0, S1PTW = 0 [ 85.884638] FSC = 0x07: level 3 translation fault [ 85.884642] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041dd0000 [ 85.884646] [ffffd4a61638f258] pgd=1000000095fff003, p4d=1000000095fff003, pud=100000004823d003, pmd=100000004823e003, pte=0000000000000000 [ 85.884662] Internal error: Oops: 0000000086000007 [#1] PREEMPT SMP [ 85.890932] Modules linked in: algif_hash algif_skcipher af_alg overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_spdif snd_soc_fsl_micfil snd_soc_fsl_sai snd_soc_fsl_utils gpio_ir_recv rc_core fuse [last unloaded: btnxpuart(O)] [ 85.927297] CPU: 1 PID: 67 Comm: kworker/1:3 Tainted: G O 6.1.36+g937b1be4345a #1 [ 85.936176] Hardware name: FSL i.MX8MM EVK board (DT) [ 85.936182] Workqueue: events 0xffffd4a61638f380 [ 85.936198] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 85.952817] pc : 0xffffd4a61638f258 [ 85.952823] lr : 0xffffd4a61638f258 [ 85.952827] sp : ffff8000084fbd70 [ 85.952829] x29: ffff8000084fbd70 x28: 0000000000000000 x27: 0000000000000000 [ 85.963112] x26: ffffd4a69133f000 x25: ffff4bf1c8540990 x24: ffff4bf215b87305 [ 85.963119] x23: ffff4bf215b87300 x22: ffff4bf1c85409d0 x21: ffff4bf1c8540970 [ 85.977382] x20: 0000000000000000 x19: ffff4bf1c8540880 x18: 0000000000000000 [ 85.977391] x17: 0000000000000000 x16: 0000000000000133 x15: 0000ffffe2217090 [ 85.977399] x14: 0000000000000001 x13: 0000000000000133 x12: 0000000000000139 [ 85.977407] x11: 0000000000000001 x10: 0000000000000a60 x9 : ffff8000084fbc50 [ 85.977417] x8 : ffff4bf215b7d000 x7 : ffff4bf215b83b40 x6 : 00000000000003e8 [ 85.977424] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : 0000000000000000 [ 85.977432] x2 : 0000000000000000 x1 : ffff4bf1c4265880 x0 : 0000000000000000 [ 85.977443] Call trace: [ 85.977446] 0xffffd4a61638f258 [ 85.977451] 0xffffd4a61638f3e8 [ 85.977455] process_one_work+0x1d4/0x330 [ 85.977464] worker_thread+0x6c/0x430 [ 85.977471] kthread+0x108/0x10c [ 85.977476] ret_from_fork+0x10/0x20 [ 85.977488] Code: bad PC value [ 85.977491] ---[ end trace 0000000000000000 ]--- Preset since v6.9.11

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix random crash seen while removing driver This fixes the random kernel crash seen while removing the driver, when running the load/unload test over multiple iterations. 1) modprobe btnxpuart 2) hciconfig hci0 reset 3) hciconfig (check hci0 interface up with valid BD address) 4) modprobe -r btnxpuart Repeat steps 1 to 4 The ps_wakeup() call in btnxpuart_close() schedules the psdata->work(), which gets scheduled after module is removed, causing a kernel crash. This hidden issue got highlighted after enabling Power Save by default in 4183a7be7700 (Bluetooth: btnxpuart: Enable Power Save feature on startup) The new ps_cleanup() deasserts UART break immediately while closing serdev device, cancels any scheduled ps_work and destroys the ps_lock mutex. [ 85.884604] Unable to handle kernel paging request at virtual address ffffd4a61638f258 [ 85.884624] Mem abort info: [ 85.884625] ESR = 0x0000000086000007 [ 85.884628] EC = 0x21: IABT (current EL), IL = 32 bits [ 85.884633] SET = 0, FnV = 0 [ 85.884636] EA = 0, S1PTW = 0 [ 85.884638] FSC = 0x07: level 3 translation fault [ 85.884642] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041dd0000 [ 85.884646] [ffffd4a61638f258] pgd=1000000095fff003, p4d=1000000095fff003, pud=100000004823d003, pmd=100000004823e003, pte=0000000000000000 [ 85.884662] Internal error: Oops: 0000000086000007 [#1] PREEMPT SMP [ 85.890932] Modules linked in: algif_hash algif_skcipher af_alg overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_spdif snd_soc_fsl_micfil snd_soc_fsl_sai snd_soc_fsl_utils gpio_ir_recv rc_core fuse [last unloaded: btnxpuart(O)] [ 85.927297] CPU: 1 PID: 67 Comm: kworker/1:3 Tainted: G O 6.1.36+g937b1be4345a #1 [ 85.936176] Hardware name: FSL i.MX8MM EVK board (DT) [ 85.936182] Workqueue: events 0xffffd4a61638f380 [ 85.936198] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 85.952817] pc : 0xffffd4a61638f258 [ 85.952823] lr : 0xffffd4a61638f258 [ 85.952827] sp : ffff8000084fbd70 [ 85.952829] x29: ffff8000084fbd70 x28: 0000000000000000 x27: 0000000000000000 [ 85.963112] x26: ffffd4a69133f000 x25: ffff4bf1c8540990 x24: ffff4bf215b87305 [ 85.963119] x23: ffff4bf215b87300 x22: ffff4bf1c85409d0 x21: ffff4bf1c8540970 [ 85.977382] x20: 0000000000000000 x19: ffff4bf1c8540880 x18: 0000000000000000 [ 85.977391] x17: 0000000000000000 x16: 0000000000000133 x15: 0000ffffe2217090 [ 85.977399] x14: 0000000000000001 x13: 0000000000000133 x12: 0000000000000139 [ 85.977407] x11: 0000000000000001 x10: 0000000000000a60 x9 : ffff8000084fbc50 [ 85.977417] x8 : ffff4bf215b7d000 x7 : ffff4bf215b83b40 x6 : 00000000000003e8 [ 85.977424] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : 0000000000000000 [ 85.977432] x2 : 0000000000000000 x1 : ffff4bf1c4265880 x0 : 0000000000000000 [ 85.977443] Call trace: [ 85.977446] 0xffffd4a61638f258 [ 85.977451] 0xffffd4a61638f3e8 [ 85.977455] process_one_work+0x1d4/0x330 [ 85.977464] worker_thread+0x6c/0x430 [ 85.977471] kthread+0x108/0x10c [ 85.977476] ret_from_fork+0x10/0x20 [ 85.977488] Code: bad PC value [ 85.977491] ---[ end trace 0000000000000000 ]--- Preset since v6.9.11

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may 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
local access → vulnerable operation → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial 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-2024-2133Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240918Security Bulletin 18 Sep 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 18 Sep 2024, published on 18 September 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-41057 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45029 Référence CVE CVE-2024-45030 https://www.cve.org/CVERecord?id=CVE-2024-45030 Référence CVE CVE-2024-46672 https://www.cve.org/CVERecord?id=CVE-2024-46672 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46678 https://www.cve.org/CVERecord?id=CVE-2024-46678 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46681 https://www.cve.org/CVERecord?id=CVE-2024-46681 Référence CVE CVE-2024-46683 https://www.cve.org/CVERecord?id=CVE-2024-46683 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46686 https://www.cve.org/CVERecord?id=CVE-2024-46686 Référence CVE CVE-2024-46687 https://www.cve.org/CVERecord?id=CVE-2024-46687 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=CVE-2024-46689 Référence CVE CVE-2024-46691 https://www.cve.org/CVERecord?id=CVE-2024-46691 Référence CVE CVE-2024-46692 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44931 Référence CVE CVE-2024-44932 https://www.cve.org/CVERecord?id=CVE-2024-44932 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44964 https://www.cve.org/CVERecord?id=CVE-2024-44964 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-46678 https://www.cve.org/CVERecord?id=CVE-2024-46678 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46681 https://www.cve.org/CVERecord?id=CVE-2024-46681 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46719 https://www.cve.org/CVERecord?id=CVE-2024-46719 Référence CVE CVE-2024-46721 https://www.cve.org/CVERecord?id=CVE-2024-46721 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46766 https://www.cve.org/CVERecord?id=CVE-2024-46766 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45029 Référence CVE CVE-2024-45030 https://www.cve.org/CVERecord?id=CVE-2024-45030 Référence CVE CVE-2024-46672 https://www.cve.org/CVERecord?id=CVE-2024-46672 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=CVE-2024-46673 Référence CVE CVE-2024-46675 https://www.cve.org/CVERecord?id=CVE-2024-46675 Référence CVE CVE-2024-46676 https://www.cve.org/CVERecord?id=CVE-2024-46676 Référence CVE CVE-2024-46677 https://www.cve.org/CVERecord?id=CVE-2024-46677 Référence CVE CVE-2024-46678 https://www.cve.org/CVERecord?id=CVE-2024-46678 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46681 https://www.cve.org/CVERecord?id=CVE-2024-46681 Référence CVE CVE-2024-46683 https://www.cve.org/CVERecord?id=CVE-2024-46683 Référence CVE CVE-2024-46685 https://www.cve.org/CVERecord?id=CVE-2024-46685 Référence CVE CVE-2024-46686 https://www.cve.org/CVERecord?id=CVE-2024-46686 Référence CVE CVE-2024-46687 https://www.cve.org/CVERecord?id=CVE-2024-46687 Référence CVE CVE-2024-46689 https://www.cve.org/CVERecord?id=CVE-2024-46689 Référence CVE CVE-2024-46691 https://www.cve.org/CVERecord?id=CVE-2024-46691 Référence CVE CVE-2024-46692 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-008978Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: 86d55f124b52de2ba0d066d89b766bcc0387fd72 < 662a55986b88807da4d112d838c8aaa05810e938, 86d55f124b52de2ba0d066d89b766bcc0387fd72 < 29a1d9971e38f92c84b363ff50379dd434ddfe1c, 86d55f124b52de2ba0d066d89b766bcc0387fd72 < 35237475384ab3622f63c3c09bdf6af6dacfe9c3, 6.4
Fixed
Linux: < 6.4, 6.6.49 ≤ 6.6.*, 6.10.8 ≤ 6.10.*, 6.11 ≤ *
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 13 Sept 2024 · Last source change 5 Aug 2026, 11:37 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-2024-41941
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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 ↗

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-2024-41941↗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-2024-46680 · cve.blacktree.nl