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

ax25: Fix netdev refcount issue

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 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority: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.24% 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 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.90-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-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-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-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
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-35819

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ax25: Fix netdev refcount issue The dev_tracker is added to ax25_cb in ax25_bind(). When the ax25 device is detaching, the dev_tracker of ax25_cb should be deallocated in ax25_kill_by_device() instead of the dev_tracker of ax25_dev. The log reported by ref_tracker is shown below: [ 80.884935] ref_tracker: reference already released. [ 80.885150] ref_tracker: allocated in: [ 80.885349] ax25_dev_device_up+0x105/0x540 [ 80.885730] ax25_device_event+0xa4/0x420 [ 80.885730] notifier_call_chain+0xc9/0x1e0 [ 80.885730] __dev_notify_flags+0x138/0x280 [ 80.885730] dev_change_flags+0xd7/0x180 [ 80.885730] dev_ifsioc+0x6a9/0xa30 [ 80.885730] dev_ioctl+0x4d8/0xd90 [ 80.885730] sock_do_ioctl+0x1c2/0x2d0 [ 80.885730] sock_ioctl+0x38b/0x4f0 [ 80.885730] __se_sys_ioctl+0xad/0xf0 [ 80.885730] do_syscall_64+0xc4/0x1b0 [ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 80.885730] ref_tracker: freed in: [ 80.885730] ax25_device_event+0x272/0x420 [ 80.885730] notifier_call_chain+0xc9/0x1e0 [ 80.885730] dev_close_many+0x272/0x370 [ 80.885730] unregister_netdevice_many_notify+0x3b5/0x1180 [ 80.885730] unregister_netdev+0xcf/0x120 [ 80.885730] sixpack_close+0x11f/0x1b0 [ 80.885730] tty_ldisc_kill+0xcb/0x190 [ 80.885730] tty_ldisc_hangup+0x338/0x3d0 [ 80.885730] __tty_hangup+0x504/0x740 [ 80.885730] tty_release+0x46e/0xd80 [ 80.885730] __fput+0x37f/0x770 [ 80.885730] __x64_sys_close+0x7b/0xb0 [ 80.885730] do_syscall_64+0xc4/0x1b0 [ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 80.893739] ------------[ cut here ]------------ [ 80.894030] WARNING: CPU: 2 PID: 140 at lib/ref_tracker.c:255 ref_tracker_free+0x47b/0x6b0 [ 80.894297] Modules linked in: [ 80.894929] CPU: 2 PID: 140 Comm: ax25_conn_rel_6 Not tainted 6.9.0-rc4-g8cd26fd90c1a #11 [ 80.895190] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qem4 [ 80.895514] RIP: 0010:ref_tracker_free+0x47b/0x6b0 [ 80.895808] Code: 83 c5 18 4c 89 eb 48 c1 eb 03 8a 04 13 84 c0 0f 85 df 01 00 00 41 83 7d 00 00 75 4b 4c 89 ff 9 [ 80.896171] RSP: 0018:ffff888009edf8c0 EFLAGS: 00000286 [ 80.896339] RAX: 1ffff1100141ac00 RBX: 1ffff1100149463b RCX: dffffc0000000000 [ 80.896502] RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff88800a0d6518 [ 80.896925] RBP: ffff888009edf9b0 R08: ffff88806d3288d3 R09: 1ffff1100da6511a [ 80.897212] R10: dffffc0000000000 R11: ffffed100da6511b R12: ffff88800a4a31d4 [ 80.897859] R13: ffff88800a4a31d8 R14: dffffc0000000000 R15: ffff88800a0d6518 [ 80.898279] FS: 00007fd88b7fe700(0000) GS:ffff88806d300000(0000) knlGS:0000000000000000 [ 80.899436] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 80.900181] CR2: 00007fd88c001d48 CR3: 000000000993e000 CR4: 00000000000006f0 ... [ 80.935774] ref_tracker: sp%d@000000000bb9df3d has 1/1 users at [ 80.935774] ax25_bind+0x424/0x4e0 [ 80.935774] __sys_bind+0x1d9/0x270 [ 80.935774] __x64_sys_bind+0x75/0x80 [ 80.935774] do_syscall_64+0xc4/0x1b0 [ 80.935774] entry_SYSCALL_64_after_hwframe+0x67/0x6f Change ax25_dev->dev_tracker to the dev_tracker of ax25_cb in order to mitigate the bug.

What

In the Linux kernel, the following vulnerability has been resolved: ax25: Fix netdev refcount issue The dev_tracker is added to ax25_cb in ax25_bind(). When the ax25 device is detaching, the dev_tracker of ax25_cb should be deallocated in ax25_kill_by_device() instead of the dev_tracker of ax25_dev. The log reported by ref_tracker is shown below: [ 80.884935] ref_tracker: reference already released. [ 80.885150] ref_tracker: allocated in: [ 80.885349] ax25_dev_device_up+0x105/0x540 [ 80.885730] ax25_device_event+0xa4/0x420 [ 80.885730] notifier_call_chain+0xc9/0x1e0 [ 80.885730] __dev_notify_flags+0x138/0x280 [ 80.885730] dev_change_flags+0xd7/0x180 [ 80.885730] dev_ifsioc+0x6a9/0xa30 [ 80.885730] dev_ioctl+0x4d8/0xd90 [ 80.885730] sock_do_ioctl+0x1c2/0x2d0 [ 80.885730] sock_ioctl+0x38b/0x4f0 [ 80.885730] __se_sys_ioctl+0xad/0xf0 [ 80.885730] do_syscall_64+0xc4/0x1b0 [ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 80.885730] ref_tracker: freed in: [ 80.885730] ax25_device_event+0x272/0x420 [ 80.885730] notifier_call_chain+0xc9/0x1e0 [ 80.885730] dev_close_many+0x272/0x370 [ 80.885730] unregister_netdevice_many_notify+0x3b5/0x1180 [ 80.885730] unregister_netdev+0xcf/0x120 [ 80.885730] sixpack_close+0x11f/0x1b0 [ 80.885730] tty_ldisc_kill+0xcb/0x190 [ 80.885730] tty_ldisc_hangup+0x338/0x3d0 [ 80.885730] __tty_hangup+0x504/0x740 [ 80.885730] tty_release+0x46e/0xd80 [ 80.885730] __fput+0x37f/0x770 [ 80.885730] __x64_sys_close+0x7b/0xb0 [ 80.885730] do_syscall_64+0xc4/0x1b0 [ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 80.893739] ------------[ cut here ]------------ [ 80.894030] WARNING: CPU: 2 PID: 140 at lib/ref_tracker.c:255 ref_tracker_free+0x47b/0x6b0 [ 80.894297] Modules linked in: [ 80.894929] CPU: 2 PID: 140 Comm: ax25_conn_rel_6 Not tainted 6.9.0-rc4-g8cd26fd90c1a #11 [ 80.895190] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qem4 [ 80.895514] RIP: 0010:ref_tracker_free+0x47b/0x6b0 [ 80.895808] Code: 83 c5 18 4c 89 eb 48 c1 eb 03 8a 04 13 84 c0 0f 85 df 01 00 00 41 83 7d 00 00 75 4b 4c 89 ff 9 [ 80.896171] RSP: 0018:ffff888009edf8c0 EFLAGS: 00000286 [ 80.896339] RAX: 1ffff1100141ac00 RBX: 1ffff1100149463b RCX: dffffc0000000000 [ 80.896502] RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff88800a0d6518 [ 80.896925] RBP: ffff888009edf9b0 R08: ffff88806d3288d3 R09: 1ffff1100da6511a [ 80.897212] R10: dffffc0000000000 R11: ffffed100da6511b R12: ffff88800a4a31d4 [ 80.897859] R13: ffff88800a4a31d8 R14: dffffc0000000000 R15: ffff88800a0d6518 [ 80.898279] FS: 00007fd88b7fe700(0000) GS:ffff88806d300000(0000) knlGS:0000000000000000 [ 80.899436] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 80.900181] CR2: 00007fd88c001d48 CR3: 000000000993e000 CR4: 00000000000006f0 ... [ 80.935774] ref_tracker: sp%d@000000000bb9df3d has 1/1 users at [ 80.935774] ax25_bind+0x424/0x4e0 [ 80.935774] __sys_bind+0x1d9/0x270 [ 80.935774] __x64_sys_bind+0x75/0x80 [ 80.935774] do_syscall_64+0xc4/0x1b0 [ 80.935774] entry_SYSCALL_64_after_hwframe+0x67/0x6f Change ax25_dev->dev_tracker to the dev_tracker of ax25_cb in order to mitigate the bug.

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ax25: Fix netdev refcount issue The dev_tracker is added to ax25_cb in ax25_bind(). When the ax25 device is detaching, the dev_tracker of ax25_cb should be deallocated in ax25_kill_by_device() instead of the dev_tracker of ax25_dev. The log reported by ref_tracker is shown below: [ 80.884935] ref_tracker: reference already released. [ 80.885150] ref_tracker: allocated in: [ 80.885349] ax25_dev_device_up+0x105/0x540 [ 80.885730] ax25_device_event+0xa4/0x420 [ 80.885730] notifier_call_chain+0xc9/0x1e0 [ 80.885730] __dev_notify_flags+0x138/0x280 [ 80.885730] dev_change_flags+0xd7/0x180 [ 80.885730] dev_ifsioc+0x6a9/0xa30 [ 80.885730] dev_ioctl+0x4d8/0xd90 [ 80.885730] sock_do_ioctl+0x1c2/0x2d0 [ 80.885730] sock_ioctl+0x38b/0x4f0 [ 80.885730] __se_sys_ioctl+0xad/0xf0 [ 80.885730] do_syscall_64+0xc4/0x1b0 [ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 80.885730] ref_tracker: freed in: [ 80.885730] ax25_device_event+0x272/0x420 [ 80.885730] notifier_call_chain+0xc9/0x1e0 [ 80.885730] dev_close_many+0x272/0x370 [ 80.885730] unregister_netdevice_many_notify+0x3b5/0x1180 [ 80.885730] unregister_netdev+0xcf/0x120 [ 80.885730] sixpack_close+0x11f/0x1b0 [ 80.885730] tty_ldisc_kill+0xcb/0x190 [ 80.885730] tty_ldisc_hangup+0x338/0x3d0 [ 80.885730] __tty_hangup+0x504/0x740 [ 80.885730] tty_release+0x46e/0xd80 [ 80.885730] __fput+0x37f/0x770 [ 80.885730] __x64_sys_close+0x7b/0xb0 [ 80.885730] do_syscall_64+0xc4/0x1b0 [ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 80.893739] ------------[ cut here ]------------ [ 80.894030] WARNING: CPU: 2 PID: 140 at lib/ref_tracker.c:255 ref_tracker_free+0x47b/0x6b0 [ 80.894297] Modules linked in: [ 80.894929] CPU: 2 PID: 140 Comm: ax25_conn_rel_6 Not tainted 6.9.0-rc4-g8cd26fd90c1a #11 [ 80.895190] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qem4 [ 80.895514] RIP: 0010:ref_tracker_free+0x47b/0x6b0 [ 80.895808] Code: 83 c5 18 4c 89 eb 48 c1 eb 03 8a 04 13 84 c0 0f 85 df 01 00 00 41 83 7d 00 00 75 4b 4c 89 ff 9 [ 80.896171] RSP: 0018:ffff888009edf8c0 EFLAGS: 00000286 [ 80.896339] RAX: 1ffff1100141ac00 RBX: 1ffff1100149463b RCX: dffffc0000000000 [ 80.896502] RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff88800a0d6518 [ 80.896925] RBP: ffff888009edf9b0 R08: ffff88806d3288d3 R09: 1ffff1100da6511a [ 80.897212] R10: dffffc0000000000 R11: ffffed100da6511b R12: ffff88800a4a31d4 [ 80.897859] R13: ffff88800a4a31d8 R14: dffffc0000000000 R15: ffff88800a0d6518 [ 80.898279] FS: 00007fd88b7fe700(0000) GS:ffff88806d300000(0000) knlGS:0000000000000000 [ 80.899436] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 80.900181] CR2: 00007fd88c001d48 CR3: 000000000993e000 CR4: 00000000000006f0 ... [ 80.935774] ref_tracker: sp%d@000000000bb9df3d has 1/1 users at [ 80.935774] ax25_bind+0x424/0x4e0 [ 80.935774] __sys_bind+0x1d9/0x270 [ 80.935774] __x64_sys_bind+0x75/0x80 [ 80.935774] do_syscall_64+0xc4/0x1b0 [ 80.935774] entry_SYSCALL_64_after_hwframe+0x67/0x6f Change ax25_dev->dev_tracker to the dev_tracker of ax25_cb in order to mitigate the bug.

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2024-1188Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

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

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

d?id=CVE-2024-35946 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35956 https://www.cve.org/CVERecord?id=CVE-2024-35956 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35971 https://www.cve.org/CVERecord?id=CVE-2024-35971 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=CVE-2024-36331 Référence CVE CVE-2024-36347 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35946 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35956 https://www.cve.org/CVERecord?id=CVE-2024-35956 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35971 https://www.cve.org/CVERecord?id=CVE-2024-35971 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=CVE-2024-36331 Référence CVE CVE-2024-36347 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27016 Référence CVE CVE-2024-27024 https://www.cve.org/CVERecord?id=CVE-2024-27024 Référence CVE CVE-2024-27079 https://www.cve.org/CVERecord?id=CVE-2024-27079 Référence CVE CVE-2024-27403 https://www.cve.org/CVERecord?id=CVE-2024-27403 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-35897 https://www.cve.org/CVERecord?id=CVE-2024-35897 Référence CVE CVE-2024-35902 https://www.cve.org/CVERecord?id=CVE-2024-35902 Référence CVE CVE-2024-35945 https://www.cve.org/CVERecord?id=CVE-2024-35945 Référence CVE CVE-2024-35971 https://www.cve.org/CVERecord?id=CVE-2024-35971 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36929 https://www.cve.org/CVERecord?id=CVE-2024-36929 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36936 https://www.cve.org/CVERecord?id=CVE-2024-36936 Référence CVE CVE-2024-36962 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35902 Référence CVE CVE-2024-35913 https://www.cve.org/CVERecord?id=CVE-2024-35913 Référence CVE CVE-2024-35915 https://www.cve.org/CVERecord?id=CVE-2024-35915 Référence CVE CVE-2024-35933 https://www.cve.org/CVERecord?id=CVE-2024-35933 Référence CVE CVE-2024-35939 https://www.cve.org/CVERecord?id=CVE-2024-35939 Référence CVE CVE-2024-35945 https://www.cve.org/CVERecord?id=CVE-2024-35945 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35965 https://www.cve.org/CVERecord?id=CVE-2024-35965 Référence CVE CVE-2024-35971 https://www.cve.org/CVERecord?id=CVE-2024-35971 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=CVE-2024-36270 Référence CVE CVE-2024-36286 https://www.cve.org/CVERecord?id=CVE-2024-36286 Référence CVE CVE-2024-36288 https://www.cve.org/CVERecord?id=CVE-2024-36288 Référence CVE CVE-2024-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36881 https://www.cve.org/CVERecord?id=CVE-2024-36881 Référence CVE CVE-2024-36907 https://www.cve.org/CVERecord?id=CVE-2024-36907 Référence CVE CVE-2024-36909 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36011 https://www.cve.org/CVERecord?id=CVE-2024-36011 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?id=CVE-2024-36014 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36001 https://www.cve.org/CVERecord?id=CVE-2024-36001 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36011 https://www.cve.org/CVERecord?id=CVE-2024-36011 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?id=CVE-2024-36014 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36028 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36000 Référence CVE CVE-2024-36001 https://www.cve.org/CVERecord?id=CVE-2024-36001 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36011 https://www.cve.org/CVERecord?id=CVE-2024-36011 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?id=CVE-2024-36014 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36028 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35991 Référence CVE CVE-2024-35992 https://www.cve.org/CVERecord?id=CVE-2024-35992 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35997 https://www.cve.org/CVERecord?id=CVE-2024-35997 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36011 https://www.cve.org/CVERecord?id=CVE-2024-36011 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?id=CVE-2024-36014 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36018 https://www.cve.org/CVERecord?id=CVE-2024-36018 Référence CVE CVE-2024-36019 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028091Linux の 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: feef318c855a361a1eccd880f33e88c460eb63b4 < 0d14f104027e30720582448706c7d6b43065c851, feef318c855a361a1eccd880f33e88c460eb63b4 < 4fee8fa86a15d7790268eea458b1aec69c695530, feef318c855a361a1eccd880f33e88c460eb63b4 < c42b073d9af4a5329b25b17390c63ab3847f30e8, feef318c855a361a1eccd880f33e88c460eb63b4 < 467324bcfe1a31ec65d0cf4aa59421d6b7a7d52b, b8c07f33aa35dacf5444e7053ed9662d1869f536, b1e0a6fc7f17500484c402ad1cd018c24dfc14b3, 7528d0f2210c3a1154186175516ed37aa970f2b1, 57cc15f5fd550316e4104eaf84b90fbc640fd7a5, b982492ec3a115e0a136856a1b2dbe32f2d21a0e, 4.14.277 < 4.15, 4.19.240 < 4.20, 5.4.190 < 5.5, 5.10.112 < 5.11, 5.15.35 < 5.16, 5.17
Fixed
Linux: < 5.17, 6.1.90 ≤ 6.1.*, 6.6.30 ≤ 6.6.*, 6.8.9 ≤ 6.8.*, 6.9 ≤ *
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 20 May 2024 · Last source change 5 Aug 2026, 11:31 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-35819
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-35819↗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-2024-36009 · cve.blacktree.nl