CVE-2023-54277 Details
Description
In the Linux kernel, the following vulnerability has been resolved: fbdev: udlfb: Fix endpoint check The syzbot fuzzer detected a problem in the udlfb driver, caused by an endpoint not having the expected type: usb 1-1: Read EDID byte 0 failed: -71 usb 1-1: Unable to get valid EDID from device/display ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 9 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.4.0-rc1-syzkaller-00016-ga4422ff22142 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023 Workqueue: usb_hub_wq hub_event RIP: 0010:usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... Call Trace: <TASK> dlfb_submit_urb+0x92/0x180 drivers/video/fbdev/udlfb.c:1980 dlfb_set_video_mode+0x21f0/0x2950 drivers/video/fbdev/udlfb.c:315 dlfb_ops_set_par+0x2a7/0x8d0 drivers/video/fbdev/udlfb.c:1111 dlfb_usb_probe+0x149a/0x2710 drivers/video/fbdev/udlfb.c:1743 The current approach for this issue failed to catch the problem because it only checks for the existence of a bulk-OUT endpoint; it doesn't check whether this endpoint is the one that the driver will actually use. We can fix the problem by instead checking that the endpoint used by the driver does exist and is bulk-OUT.
A vulnerability in the Linux kernel's udlfb driver has been addressed, which was identified by the syzbot fuzzer. The issue arose because a USB endpoint did not have the expected type, leading to a failure in reading the EDID from a connected device or display. This discrepancy triggered a warning about a bogus USB transfer, indicating a mismatch between the expected and actual endpoint types. The problem was caused by the driver's endpoint check, which only verified the existence of a bulk-out endpoint without ensuring it was the one actually used by the driver. The vulnerability affected Linux kernel versions prior to 6.4.0-rc1.
Users can upgrade to the latest version of the Linux kernel to address this vulnerability. The issue has been fixed in the official Linux Git repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1522dc58bff87af79461b96d90ec122e9e726004 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/58ecc165abdaed85447455e6dc396758e8c6f219 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/9e12c58a5ece41be72157cef348576b135c9fc72 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/c8fdf7feca77cd99e25ef0a1e9e72dfc83add8ef | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/e19383e5dee5adbf3d19f3f210f440a88d1b7dde | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ed9de4ed39875706607fb08118a58344ae6c5f42 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 30, 2025 | New CVE Received | kernel.org |
Volerion