Skip to content
Fencer Vulns
medium 4.9

CVE-2007-3513 json

The lcd_write function in drivers/usb/misc/usblcd.c in the Linux kernel before 2.6.22-rc7 does not limit the amount of memory used by a cal…

published 2007-07-03 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-3497

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

The lcd_write function in drivers/usb/misc/usblcd.c in the Linux kernel before 2.6.22-rc7 does not limit the amount of memory used by a caller, which allows local users to cause a denial of service (memory consumption).

Patch / fix

  • kernel RHEL 5 2.6.18-8.1.15.el5
  • kernel-PAE RHEL 5 2.6.18-8.1.15.el5
  • kernel-xen RHEL 5 2.6.18-8.1.15.el5
  • kernel-kdump RHEL 5 2.6.18-8.1.15.el5
  • kernel-debuginfo-common RHEL 5 2.6.18-8.1.15.el5

red hat advisories RHSA-2007:0940

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2007-3513 updated

Locally triggerable memory consumption in usblcd

  • Red Hat Enterprise Linux (v. 5 server) kernel 2.6.18-8.1.15.el5, kernel-PAE 2.6.18-8.1.15.el5, kernel-xen 2.6.18-8.1.15.el5, kernel-kdump 2.6.18-8.1.15.el5, kernel-debuginfo-common 2.6.18-8.1.15.el5 Red Hat Enterprise Linux Desktop (v. 5 client) kernel 2.6.18-8.1.15.el5, kernel-PAE 2.6.18-8.1.15.el5, kernel-xen 2.6.18-8.1.15.el5, kernel-kdump 2.6.18-8.1.15.el5, kernel-debuginfo-common 2.6.18-8.1.15.el5
    fixed: vendor fix RHSA-2007:0940

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.