CVE-2021-46914

Source
https://nvd.nist.gov/vuln/detail/CVE-2021-46914
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2021-46914.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2021-46914
Related
Published
2024-02-27T07:15:07Z
Modified
2024-09-11T02:00:06Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

ixgbe: fix unbalanced device enable/disable in suspend/resume

pcidisabledevice() called in _ixgbeshutdown() decreases dev->enablecnt by 1. pcienabledevicemem() which increases dev->enablecnt by 1, was removed from ixgberesume() in commit 6f82b2558735 ("ixgbe: use generic power management"). This caused unbalanced increase/decrease. So add pcienabledevice_mem() back.

Fix the following call trace.

ixgbe 0000:17:00.1: disabling already-disabled device Call Trace: _ixgbeshutdown+0x10a/0x1e0 [ixgbe] ixgbesuspend+0x32/0x70 [ixgbe] pcipmsuspend+0x87/0x160 ? pcipmfreeze+0xd0/0xd0 dpmruncallback+0x42/0x170 _devicesuspend+0x114/0x460 asyncsuspend+0x1f/0xa0 asyncrunentryfn+0x3c/0xf0 processonework+0x1dd/0x410 workerthread+0x34/0x3f0 ? canceldelayedwork+0x90/0x90 kthread+0x14c/0x170 ? kthreadpark+0x90/0x90 retfrom_fork+0x1f/0x30

References

Affected packages

Debian:11 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.38-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.38-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.38-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}