CVE-2025-11961 | OOBR and OOBW in pcap_ether_aton() in libpcap

pcap_ether_aton() is an auxiliary function in libpcap, it takes a string argument and returns a fixed-size allocated buffer. The string argument must be a well-formed MAC-48 address in one of the supported formats, but this requirement has been poorly documented. If an application calls the function with an argument that deviates from the expected format, the function can read data beyond the end of the provided string and write data beyond the end of the allocated buffer.

Published: 2025-12-31 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-11961 is rated Low Risk (8.1/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.10%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-11961

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.10% +0.09%
2 2025-12-31 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-11961

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
1.9 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 0.5 1.4 [email protected]

Weakness enumeration for CVE-2025-11961

OS Trackers for CVE-2025-11961

vendor priority summary link
alpine low CVE-2025-11961: 1 source package rows (libpcap); 12 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 12. https://security.alpinelinux.org/vuln/CVE-2025-11961
debian not yet assigned CVE-2025-11961 not yet assigned priority: Debian including 1 source packages (libpcap), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-11961
redhat low — https://access.redhat.com/security/cve/CVE-2025-11961
suse low CVE-2025-11961 severity low: SUSE including 266 source package names (13.2-9.1:gpg2-2.4.4-4.1, 13.2-9.1:pam-1.6.0-4.1, …), 475 product×package rows across 207 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (207 product lines)): Fixed 242, Known Affected 231, First Fixed 2. https://www.suse.com/security/cve/CVE-2025-11961/
ubuntu low CVE-2025-11961 low priority: Ubuntu including 1 source packages (libpcap), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-11961

Affected software / configurations for CVE-2025-11961

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-11961

cvelogic Threat Intelligence