Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50040: igb: Do not bring the device up after non-fatal error

Noroxi assessment

Priority: Monitor (action score 22/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.25% (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 0a94079e3841d00ea5abb05e3233d019a86745f6, 330a699ecbfc9c26ec92c6310686da1230b4e7eb, 4.15; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1.

Low priority for now. Upgrade to Linux Linux 0a94079e3841d00ea5abb05e3233d019a86745f6, 330a699ecbfc9c26ec92c6310686da1230b4e7eb, 4.15; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1 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: igb: Do not bring the device up after non-fatal error Commit 004d25060c78 ("igb: Fix igb_down hung on surprise removal") changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below. [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [ T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [ T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ T292] igb 0000:09:00.0: device [8086:1537] error status/mask=00004000/00000000 [ T292] igb 0000:09:00.0: [14] CmpltTO [ 200.105524,009][ T292] igb 0000:09:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000 [ T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [ T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [ T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [ T292] pcieport 0000:00:1c.5: AER: broadcast resume message [ T292] ------------[ cut here ]------------ [ T292] kernel BUG at net/core/dev.c:6539! [ T292] invalid opcode: 0000 [#1] PREEMPT SMP [ T292] RIP: 0010:napi_enable+0x37/0x40 [ T292] Call Trace: [ T292] <TASK> [ T292] ? die+0x33/0x90 [ T292] ? do_trap+0xdc/0x110 [ T292] ? napi_enable+0x37/0x40 [ T292] ? do_error_trap+0x70/0xb0 [ T292] ? napi_enable+0x37/0x40 [ T292] ? napi_enable+0x37/0x40 [ T292] ? exc_invalid_op+0x4e/0x70 [ T292] ? napi_enable+0x37/0x40 [ T292] ? asm_exc_invalid_op+0x16/0x20 [ T292] ? napi_enable+0x37/0x40 [ T292] igb_up+0x41/0x150 [ T292] igb_io_resume+0x25/0x70 [ T292] report_resume+0x54/0x70 [ T292] ? report_frozen_detected+0x20/0x20 [ T292] pci_walk_bus+0x6c/0x90 [ T292] ? aer_print_port_info+0xa0/0xa0 [ T292] pcie_do_recovery+0x22f/0x380 [ T292] aer_process_err_devices+0x110/0x160 [ T292] aer_isr+0x1c1/0x1e0 [ T292] ? disable_irq_nosync+0x10/0x10 [ T292] irq_thread_fn+0x1a/0x60 [ T292] irq_thread+0xe3/0x1a0 [ T292] ? irq_set_affinity_notifier+0x120/0x120 [ T292] ? irq_affinity_notify+0x100/0x100 [ T292] kthread+0xe2/0x110 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork+0x2d/0x50 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork_asm+0x11/0x20 [ T292] </TASK> To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 17th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-50040

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

Running WordPress? Scan your site free with WP Lens

  • 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

Running WordPress? Scan your site free with WP Lens

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 kernel4.14.322 and later · before 4.15
  • linux linux kernel4.19.291 and later · before 4.20
  • linux linux kernel5.4.251 and later · before 5.5
  • linux linux kernel5.10.188 and later · before 5.10.227
  • linux linux kernel5.15.150 and later · before 5.15.168
  • linux linux kernel6.1.42 and later · before 6.1.113
  • linux linux kernel6.4.7 and later · before 6.5
  • linux linux kernel6.5 and later · before 6.6.57
  • linux linux kernel6.7 and later · before 6.11.4
  • linux linux kernel6.12

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

    • c2312e1d12b1c3ee4100c173131b102e2aed4d04, 41f63b72a01c0e0ac59ab83fd2d921fcce0f602d, 6.5affected
    • 124e39a734cb90658b8f0dc110847bbfc6e33792 and later · before dca2ca65a8695d9593e2cf1b40848e073ad75413affected · git
    • c9f56f3c7bc908caa772112d3ae71cdd5d18c257 and later · before c92cbd283ddcf55fd85a9a9b0ba13298213f3dd7affected · git
    • 994c2ceb70ea99264ccc6f09e6703ca267dad63c and later · before d79af3af2f49c6aae9add3d492c04d60c1b85ce4affected · git
    • fa92c463eba75dcedbd8d689ffdcb83293aaa0c3 and later · before 0a94079e3841d00ea5abb05e3233d019a86745f6affected · git
    • 39695e87d86f0e7d897fba1d2559f825aa20caeb and later · before 6a39c8f5c8aae74c5ab2ba466791f59ffaab0178affected · git
    • 004d25060c78fc31f66da0fa439c544dda1ac9d5 and later · before 57c5053eaa5f9a8a99e34732e37a86615318e464affected · git
    • 004d25060c78fc31f66da0fa439c544dda1ac9d5 and later · before 500be93c5d53b7e2c5314292012185f0207bad0caffected · git
    • 004d25060c78fc31f66da0fa439c544dda1ac9d5 and later · before 330a699ecbfc9c26ec92c6310686da1230b4e7ebaffected · git
    • 4.19.291 and later · before 4.19.323affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

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-50035Oct 21, 2024 · ppp: fix ppp_async_encode() illegal access
    28Monitor
  • ← EarlierCVE-2024-50039Oct 21, 2024 · net/sched: accept TCA_STAB only for root qdisc
    22Monitor
  • Later →CVE-2024-50043Oct 21, 2024 · nfsd: fix possible badness in FREE_STATEID
    31Monitor

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 Linux0a94079e3841d00ea5abb05e3233d019a86745f6Vendor (CNA)
Linux Linux330a699ecbfc9c26ec92c6310686da1230b4e7ebVendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.19.323Vendor (CNA)
Linux Linux5.10.227Vendor (CNA)
Linux Linux5.15.168Vendor (CNA)
Linux Linux5.4.285Vendor (CNA)
Linux Linux500be93c5d53b7e2c5314292012185f0207bad0cVendor (CNA)
Linux Linux57c5053eaa5f9a8a99e34732e37a86615318e464Vendor (CNA)
Linux Linux6.1.113Vendor (CNA)
Linux Linux6.5Vendor (CNA)
Linux Linux6a39c8f5c8aae74c5ab2ba466791f59ffaab0178Vendor (CNA)
Linux Linuxc92cbd283ddcf55fd85a9a9b0ba13298213f3dd7Vendor (CNA)
Linux Linuxd79af3af2f49c6aae9add3d492c04d60c1b85ce4Vendor (CNA)
Linux Linuxdca2ca65a8695d9593e2cf1b40848e073ad75413Vendor (CNA)
azl3 kernel 6.6.56.1-5 on Azure Linux 3.06.6.57.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.57.1-1 on Azure Linux 3.06.6.57.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

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).

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

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 (12 more)

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

All records