LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54277: fbdev: udlfb: Fix endpoint check

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-54277 is a Linux kernel driver flaw in udlfb, used for some USB framebuffer/display devices. A malformed or unexpected USB endpoint could trigger an invalid USB transfer path and kernel warning. The source bundle does not provide CVSS, confirmed business impact, or active exploitation evidence.

Executive priority

Handle through normal kernel patch management unless the organization permits untrusted USB devices. Raise priority for shared workstations, kiosks, labs, or virtualization hosts where USB attachment is less controlled.

Technical view

The udlfb driver checked only for any bulk-OUT endpoint, not whether the endpoint it would actually use existed and was bulk-OUT. The fix validates the specific driver-selected endpoint before use, preventing the syzbot-reported invalid URB submission path in usb_submit_urb.

Likely exposure

Exposure is likely limited to Linux systems with the udlfb driver present and reachable through USB display-device attachment. Desktops, kiosks, lab systems, or virtualized environments allowing untrusted USB devices deserve review. Exact distribution impact must be confirmed through vendor kernel advisories.

Exploitation context

The provided sources describe syzbot fuzzing and kernel fixes. They do not cite public exploitation, CISA KEV listing, or weaponized activity. Treat exploitation status as unconfirmed, with risk driven by USB device trust boundaries and local hardware access.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. The issue is in endpoint validation, not a documented remote attack. Further impact analysis requires kernel advisory context, distro backport mapping, and local udlfb usage evidence.

Mitigation direction

  • Apply Linux vendor kernel updates containing the referenced udlfb fix.
  • Prioritize systems accepting untrusted or removable USB display devices.
  • Disable or avoid loading udlfb where USB framebuffer support is unnecessary.
  • Restrict USB passthrough and device attachment in virtualized or shared environments.
  • Track distribution advisories for backported fixes and support status.

Validation and detection

  • Inventory running kernel versions and distribution package advisory status.
  • Check whether the udlfb module is available, loaded, or required.
  • Review USB exposure on desktops, kiosks, labs, and virtual hosts.
  • Confirm patched kernels include the referenced stable commits or vendor backports.
  • Monitor logs for udlfb or USB URB warnings on exposed systems.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54277 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf6db63819db632158647d5bbf4d7d2d90dc1a268, c4fb41bdf4d6ccca850c4af5d707d14a0fb717a7, 4df1584738f1dc6f0dd854d258bba48591f1ed0e, aaf7dbe07385e0b8deb7237eca2a79926bbc7091, aaf7dbe07385e0b8deb7237eca2a79926bbc7091, aaf7dbe07385e0b8deb7237eca2a79926bbc7091, 895ea8a290ba87850bcaf2ecfcddef75a014fa54, 5.4.192, 5.10.114, 5.15.38, 5.17.6unaffected
LinuxLinux5.18, 0, 5.4.244, 5.10.181, 5.15.114, 6.1.31, 6.3.5, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.