Skip to content
Fencer Vulns
high 7.2

CVE-2003-0961 json

Integer overflow in the do_brk function for the brk system call in Linux kernel 2.4.22 and earlier allows local users to gain root privileg…

published 2003-12-02 22 y ago modified 2026-06-16 4 mo ago also EUVD-2003-0951

cvss
7.2
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.9%
EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits
2
Exploit-DB

Summary

Integer overflow in the do_brk function for the brk system call in Linux kernel 2.4.22 and earlier allows local users to gain root privileges.

Patch / fix

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-2003-0961 updated

security flaw

  • Red Hat Enterprise Linux AS version 3
    fixed: vendor fix RHBA-2003:308
  • Red Hat Enterprise Linux ES version 2.1 Red Hat Enterprise Linux WS version 2.1
    fixed: vendor fix RHSA-2003:389
  • Red Hat Enterprise Linux WS version 3
    fixed: vendor fix RHBA-2003:308
  • Red Hat Linux 7.1 Red Hat Linux 7.2 Red Hat Linux 7.3 Red Hat Linux 8.0 Red Hat Linux 9
    fixed: vendor fix RHSA-2003:392
  • Red Hat Linux Advanced Workstation 2.1
    fixed: vendor fix RHSA-2003:368

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

Timeline

  1. First public exploit (EDB-129)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-131 Linux Kernel 2.4.22 - 'do_brk()' Local Privilege Escalation (2) local, 2003-12-05
  • EDB-129 Linux Kernel 2.4.22 - 'do_brk()' Local Privilege Escalation (1) local, 2003-12-02

CVSS scores

assigned by version score vector
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/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.