DEBIAN-CVE-2023-53463

Source
https://security-tracker.debian.org/tracker/CVE-2023-53463
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53463.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2023-53463
Upstream
Published
2025-10-01T12:15:48Z
Modified
2025-10-02T09:16:48.933649Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Do not reset dql stats on NONFATAL err All ibmvnic resets, make a call to netdevtxresetqueue() when re-opening the device. netdevtxresetqueue() resets the numqueued and numcompleted byte counters. These stats are used in Byte Queue Limit (BQL) algorithms. The difference between these two stats tracks the number of bytes currently sitting on the physical NIC. ibmvnic increases the number of queued bytes though calls to netdevtxsentqueue() in the drivers xmit function. When, VIOS reports that it is done transmitting bytes, the ibmvnic device increases the number of completed bytes through calls to netdevtxcompletedqueue(). It is important to note that the driver batches its transmit calls and numqueued is increased every time that an skb is added to the next batch, not necessarily when the batch is sent to VIOS for transmission. Unlike other reset types, a NON FATAL reset will not flush the sub crq tx buffers. Therefore, it is possible for the batched skb array to be partially full. So if there is call to netdevtxresetqueue() when re-opening the device, the value of numqueued (0) would not account for the skb's that are currently batched. Eventually, when the batch is sent to VIOS, the call to netdevtxcompletedqueue() would increase numcompleted to a value greater than the numqueued. This causes a BUGON crash: ibmvnic 30000002: Firmware reports error, cause: adapter problem. Starting recovery... ibmvnic 30000002: tx error 600 ibmvnic 30000002: tx error 600 ibmvnic 30000002: tx error 600 ibmvnic 30000002: tx error 600 ------------[ cut here ]------------ kernel BUG at lib/dynamicqueuelimits.c:27! Oops: Exception in kernel mode, sig: 5 [....] NIP dqlcompleted+0x28/0x1c0 LR ibmvniccompletetx.isra.0+0x23c/0x420 [ibmvnic] Call Trace: ibmvniccompletetx.isra.0+0x3f8/0x420 [ibmvnic] (unreliable) ibmvnicinterrupttx+0x40/0x70 [ibmvnic] _handleirqeventpercpu+0x98/0x270 ---[ end trace ]--- Therefore, do not reset the dql stats when performing a NONFATAL reset.

References

Affected packages

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
6.1.52-1

Affected versions

6.*

6.1.27-1
6.1.37-1
6.1.38-1
6.1.38-2~bpo11+1
6.1.38-2
6.1.38-3
6.1.38-4~bpo11+1
6.1.38-4

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
6.4.4-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:14 / 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
6.4.4-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}