Description

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.

Metrics

 

CVSS Version 4.0 CVSS Version 3.x CVSS Version 2.0

NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.

CVSS 4.0 Severity and Vector Strings:

NIST: NVD

N/A

NVD assessment not yet provided.

CVSS 3.x Severity and Vector Strings:

NIST: NVD

Base Score:  5.5 MEDIUM

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

CVSS 2.0 Severity and Vector Strings:

NIST: NVD

Base Score: N/A

NVD assessment not yet provided.

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Hyperlink	Resource
https://git.kernel.org/stable/c/0a94079e3841d00ea5abb05e3233d019a86745f6	Patch
https://git.kernel.org/stable/c/330a699ecbfc9c26ec92c6310686da1230b4e7eb	Patch
https://git.kernel.org/stable/c/500be93c5d53b7e2c5314292012185f0207bad0c	Patch
https://git.kernel.org/stable/c/57c5053eaa5f9a8a99e34732e37a86615318e464	Patch
https://git.kernel.org/stable/c/6a39c8f5c8aae74c5ab2ba466791f59ffaab0178	Patch
https://git.kernel.org/stable/c/d79af3af2f49c6aae9add3d492c04d60c1b85ce4	Patch

Weakness Enumeration

CWE-ID	CWE Name	Source
NVD-CWE-noinfo	Insufficient Information	NIST

Known Affected Software Configurations Switch to CPE 2.2

CPEs loading, please wait.

Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.

Change History

2 change records found show changes

Initial Analysis by NIST 10/25/2024 11:49:33 AM

Action	Type	Old Value	New Value
Added	CPE Configuration		Record truncated, showing 500 of 1092 characters. View Entire Change Record OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.14.322 up to (excluding) 4.15 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.291 up to (excluding) 4.20 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.251 up to (excluding) 5.5 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.188 up to (excluding) 5.10.227 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions
Added	CVSS V3.1		NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Added	CWE		NIST NVD-CWE-noinfo
Changed	Reference Type	https://git.kernel.org/stable/c/0a94079e3841d00ea5abb05e3233d019a86745f6 No Types Assigned	https://git.kernel.org/stable/c/0a94079e3841d00ea5abb05e3233d019a86745f6 Patch
Changed	Reference Type	https://git.kernel.org/stable/c/330a699ecbfc9c26ec92c6310686da1230b4e7eb No Types Assigned	https://git.kernel.org/stable/c/330a699ecbfc9c26ec92c6310686da1230b4e7eb Patch
Changed	Reference Type	https://git.kernel.org/stable/c/500be93c5d53b7e2c5314292012185f0207bad0c No Types Assigned	https://git.kernel.org/stable/c/500be93c5d53b7e2c5314292012185f0207bad0c Patch
Changed	Reference Type	https://git.kernel.org/stable/c/57c5053eaa5f9a8a99e34732e37a86615318e464 No Types Assigned	https://git.kernel.org/stable/c/57c5053eaa5f9a8a99e34732e37a86615318e464 Patch
Changed	Reference Type	https://git.kernel.org/stable/c/6a39c8f5c8aae74c5ab2ba466791f59ffaab0178 No Types Assigned	https://git.kernel.org/stable/c/6a39c8f5c8aae74c5ab2ba466791f59ffaab0178 Patch
Changed	Reference Type	https://git.kernel.org/stable/c/d79af3af2f49c6aae9add3d492c04d60c1b85ce4 No Types Assigned	https://git.kernel.org/stable/c/d79af3af2f49c6aae9add3d492c04d60c1b85ce4 Patch

New CVE Received by NIST 10/21/2024 4:15:17 PM

Action	Type	Old Value	New Value
Added	Description		Record truncated, showing 500 of 2871 characters. View Entire Change Record 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
Added	Reference		kernel.org https://git.kernel.org/stable/c/0a94079e3841d00ea5abb05e3233d019a86745f6 [No types assigned]
Added	Reference		kernel.org https://git.kernel.org/stable/c/330a699ecbfc9c26ec92c6310686da1230b4e7eb [No types assigned]
Added	Reference		kernel.org https://git.kernel.org/stable/c/500be93c5d53b7e2c5314292012185f0207bad0c [No types assigned]
Added	Reference		kernel.org https://git.kernel.org/stable/c/57c5053eaa5f9a8a99e34732e37a86615318e464 [No types assigned]
Added	Reference		kernel.org https://git.kernel.org/stable/c/6a39c8f5c8aae74c5ab2ba466791f59ffaab0178 [No types assigned]
Added	Reference		kernel.org https://git.kernel.org/stable/c/d79af3af2f49c6aae9add3d492c04d60c1b85ce4 [No types assigned]