Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-39502: ionic: fix use after netif_napi_del()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0d19267cb150e8f76ade210e16ee820a77f684e7, 183ebc167a8a19e916b885d4bb61a3491991bfa5, 60cd714871cd5a683353a355cbb17a685245cf84.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0d19267cb150e8f76ade210e16ee820a77f684e7, 183ebc167a8a19e916b885d4bb61a3491991bfa5, 60cd714871cd5a683353a355cbb17a685245cf84 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ionic: fix use after netif_napi_del() When queues are started, netif_napi_add() and napi_enable() are called. If there are 4 queues and only 3 queues are used for the current configuration, only 3 queues' napi should be registered and enabled. The ionic_qcq_enable() checks whether the .poll pointer is not NULL for enabling only the using queue' napi. Unused queues' napi will not be registered by netif_napi_add(), so the .poll pointer indicates NULL. But it couldn't distinguish whether the napi was unregistered or not because netif_napi_del() doesn't reset the .poll pointer to NULL. So, ionic_qcq_enable() calls napi_enable() for the queue, which was unregistered by netif_napi_del(). Reproducer: ethtool -L <interface name> rx 1 tx 1 combined 0 ethtool -L <interface name> rx 0 tx 0 combined 1 ethtool -L <interface name> rx 0 tx 0 combined 4 Splat looks like: kernel BUG at net/core/dev.c:6666! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 1057 Comm: kworker/3:3 Not tainted 6.10.0-rc2+ #16 Workqueue: events ionic_lif_deferred_work [ionic] RIP: 0010:napi_enable+0x3b/0x40 Code: 48 89 c2 48 83 e2 f6 80 b9 61 09 00 00 00 74 0d 48 83 bf 60 01 00 00 00 74 03 80 ce 01 f0 4f RSP: 0018:ffffb6ed83227d48 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff97560cda0828 RCX: 0000000000000029 RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff97560cda0a28 RBP: ffffb6ed83227d50 R08: 0000000000000400 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000 R13: ffff97560ce3c1a0 R14: 0000000000000000 R15: ffff975613ba0a20 FS: 0000000000000000(0000) GS:ffff975d5f780000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8f734ee200 CR3: 0000000103e50000 CR4: 00000000007506f0 PKRU: 55555554 Call Trace: <TASK> ? die+0x33/0x90 ? do_trap+0xd9/0x100 ? napi_enable+0x3b/0x40 ? do_error_trap+0x83/0xb0 ? napi_enable+0x3b/0x40 ? napi_enable+0x3b/0x40 ? exc_invalid_op+0x4e/0x70 ? napi_enable+0x3b/0x40 ? asm_exc_invalid_op+0x16/0x20 ? napi_enable+0x3b/0x40 ionic_qcq_enable+0xb7/0x180 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_start_queues+0xc4/0x290 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_link_status_check+0x11c/0x170 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_lif_deferred_work+0x129/0x280 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] process_one_work+0x145/0x360 worker_thread+0x2bb/0x3d0 ? __pfx_worker_thread+0x10/0x10 kthread+0xcc/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2d/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 12, 2024
Updated
Oct 15, 2026
EPSS
0.3% · 23th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-39502

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.4 and later · before 5.4.279
  • linux linux kernel5.5 and later · before 5.10.221
  • linux linux kernel5.11 and later · before 5.15.162
  • linux linux kernel5.16 and later · before 6.1.95
  • linux linux kernel6.2 and later · before 6.6.35
  • linux linux kernel6.7 and later · before 6.9.6
  • linux linux kernel6.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.4affected
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before 0d19267cb150e8f76ade210e16ee820a77f684e7affected · git
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before ff9c2a9426ecf5b9631e9fd74993b357262387d6affected · git
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before 8edd18dab443863e9e48f084e7f123fca3065e4eaffected · git
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before 60cd714871cd5a683353a355cbb17a685245cf84affected · git
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before 183ebc167a8a19e916b885d4bb61a3491991bfa5affected · git
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before a87d72b37b9ec2c1e18fe36b09241d8b30334a2eaffected · git
    • 0f3154e6bcb354968cc04f7cd86ce466f7b9a814 and later · before 79f18a41dd056115d685f3b0a419c7cd40055e13affected · git
    • before 5.4not affected · semver
    • 5.4.279 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.40.1.el9_47.3.0-427.40.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.40.1.el9_45.14.0-427.40.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-41002Jul 12, 2024 · crypto: hisilicon/sec - Fix memory leak for sec resource release
    22Monitor
  • ← EarlierCVE-2024-41003Jul 12, 2024 · bpf: Fix reg_set_min_max corruption of fake_reg
    31Monitor
  • Later →CVE-2024-39503Jul 12, 2024 · netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0d19267cb150e8f76ade210e16ee820a77f684e7Vendor (CNA)
Linux Linux183ebc167a8a19e916b885d4bb61a3491991bfa5Vendor (CNA)
Linux Linux60cd714871cd5a683353a355cbb17a685245cf84Vendor (CNA)
Linux Linux79f18a41dd056115d685f3b0a419c7cd40055e13Vendor (CNA)
Linux Linux8edd18dab443863e9e48f084e7f123fca3065e4eVendor (CNA)
Linux Linuxa87d72b37b9ec2c1e18fe36b09241d8b30334a2eVendor (CNA)
Linux Linuxff9c2a9426ecf5b9631e9fd74993b357262387d6Vendor (CNA)
almalinux:bpftool7.3.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.40.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.99-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-core0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:5.14.0-70.112.1.rt21.184.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records