CVE-2023-53463

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Do not reset dql stats on NON_FATAL err All ibmvnic resets, make a call to netdev_tx_reset_queue() when re-opening the device. netdev_tx_reset_queue() resets the num_queued and num_completed 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 netdev_tx_sent_queue() 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 netdev_tx_completed_queue(). It is important to note that the driver batches its transmit calls and num_queued 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 netdev_tx_reset_queue() when re-opening the device, the value of num_queued (0) would not account for the skb's that are currently batched. Eventually, when the batch is sent to VIOS, the call to netdev_tx_completed_queue() would increase num_completed to a value greater than the num_queued. This causes a BUG_ON 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/dynamic_queue_limits.c:27! Oops: Exception in kernel mode, sig: 5 [....] NIP dql_completed+0x28/0x1c0 LR ibmvnic_complete_tx.isra.0+0x23c/0x420 [ibmvnic] Call Trace: ibmvnic_complete_tx.isra.0+0x3f8/0x420 [ibmvnic] (unreliable) ibmvnic_interrupt_tx+0x40/0x70 [ibmvnic] __handle_irq_event_percpu+0x98/0x270 ---[ end trace ]--- Therefore, do not reset the dql stats when performing a NON_FATAL reset.

• https://git.kernel.org/stable/c/48538ccb825b05544ec308a509e2cc9c013402dbPatch
• https://git.kernel.org/stable/c/91a0632e73070928aafeb36b3cc676843c716931Patch
• https://git.kernel.org/stable/c/b8aedf29db1280c83191fc9579ae605791faf97fPatch
• https://git.kernel.org/stable/c/f67ef8f9f6776e2b2073cad7c5cf29de850f83d7Patch

Published

Oct 1, 2025

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-53458In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53459In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-5346Type confusion in V8 in Google Chrome prior to 117.0.5938.14…8.8
• CVE-2023-53460In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53461In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53462In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53464In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53465In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2023-53466In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53467In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53468In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53469Rejected reason: This CVE ID has been rejected or withdrawn …