BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-11961High confidence

OOBR and OOBW in pcap_ether_aton() in libpcap

The Tcpdump Group · libpcap

1.9LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs The Tcpdump Group libpcap and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainlibpcapVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.10.7-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainlibpcapVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.10.7-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainlibpcapVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.10.7-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcelibpcapAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelibpcapAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelibpcapVendor fix publishedDebian records a fixed source-package version for this release.1.10.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelibpcapVendor fix publishedDebian records a fixed source-package version for this release.1.10.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelibpcapUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-11961 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylibpcap: libpcap: Memory corruption via malformed MAC-48 address input
13 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • libpcap-devel as a component of Red Hat Enterprise Linux 10
  • libpcap.src as a component of Red Hat Enterprise Linux 10
  • libpcap-devel as a component of Red Hat Enterprise Linux 6
  • libpcap.src as a component of Red Hat Enterprise Linux 6
  • libpcap-devel as a component of Red Hat Enterprise Linux 7
  • libpcap.src as a component of Red Hat Enterprise Linux 7
  • libpcap as a component of Red Hat Enterprise Linux 8
  • libpcap-devel as a component of Red Hat Enterprise Linux 8
  • libpcap.src as a component of Red Hat Enterprise Linux 8
  • libpcap-devel as a component of Red Hat Enterprise Linux 9
  • libpcap.src as a component of Red Hat Enterprise Linux 9
  • openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in libpcap. The pcap_ether_aton() function, which processes MAC-48 addresses, does not properly validate input strings. An application that calls this function with a malformed address string can cause the function to read or write data beyond its intended memory boundaries. This can lead to minor data corruption or unexpected application behavior.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-205869

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 15 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

How

An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

How

An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Buffer Over-read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-126 ↗

CWE-126: Buffer Over-read. The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-126
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260107Security Bulletin 07 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 07 Jan 2026, published on 7 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

g/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-11234 https://www.cve.org/CVERecord?id=CVE-2025-11234 Référence CVE CVE-2025-1125 https://www.cve.org/CVERecord?id=CVE-2025-1125 Référence CVE CVE-2025-1150 https://www.cve.org/CVERecord?id=CVE-2025-1150 Référence CVE CVE-2025-1151 https://www.cve.org/CVERecord?id=CVE-2025-1151 Référence CVE CVE-2025-1152 https://www.cve.org/CVERecord?id=CVE-2025-1152 Référence CVE CVE-2025-11731 https://www.cve.org/CVERecord?id=CVE-2025-11731 Référence CVE CVE-2025-1180 https://www.cve.org/CVERecord?id=CVE-2025-1180 Référence CVE CVE-2025-11961 https://www.cve.org/CVERecord?id=CVE-2025-11961 Référence CVE CVE-2025-12084 https://www.cve.org/CVERecord?id=CVE-2025-12084 Référence CVE CVE-2025-1272 https://www.cve.org/CVERecord?id=CVE-2025-1272 Référence CVE CVE-2025-12801 https://www.cve.org/CVERecord?id=CVE-2025-12801 Référence CVE CVE-2025-13462 https://www.cve.org/CVERecord?id=CVE-2025-13462 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-1352 https://www.cve.org/CVERecord?id=CVE-2025-1352 Référence CVE CVE-2025-1369 https://www.cve.org/CVERecord?id=CVE-2025-1369 Référence CVE CVE-2025-13735 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

rg/CVERecord?id=CVE-2025-1118 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-11234 https://www.cve.org/CVERecord?id=CVE-2025-11234 Référence CVE CVE-2025-1125 https://www.cve.org/CVERecord?id=CVE-2025-1125 Référence CVE CVE-2025-1150 https://www.cve.org/CVERecord?id=CVE-2025-1150 Référence CVE CVE-2025-1151 https://www.cve.org/CVERecord?id=CVE-2025-1151 Référence CVE CVE-2025-1152 https://www.cve.org/CVERecord?id=CVE-2025-1152 Référence CVE CVE-2025-11731 https://www.cve.org/CVERecord?id=CVE-2025-11731 Référence CVE CVE-2025-1180 https://www.cve.org/CVERecord?id=CVE-2025-1180 Référence CVE CVE-2025-11961 https://www.cve.org/CVERecord?id=CVE-2025-11961 Référence CVE CVE-2025-1272 https://www.cve.org/CVERecord?id=CVE-2025-1272 Référence CVE CVE-2025-12801 https://www.cve.org/CVERecord?id=CVE-2025-12801 Référence CVE CVE-2025-13462 https://www.cve.org/CVERecord?id=CVE-2025-13462 Référence CVE CVE-2025-1352 https://www.cve.org/CVERecord?id=CVE-2025-1352 Référence CVE CVE-2025-1369 https://www.cve.org/CVERecord?id=CVE-2025-1369 Référence CVE CVE-2025-13735 https://www.cve.org/CVERecord?id=CVE-2025-13735 Référence CVE CVE-2025-1376 https://www.cve.org/CVERecord?id=CVE-2025-1376 Référence CVE CVE-2025-14017 https://www.cve.org/CVERecord?id=CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0022Multiples vulnérabilités dans les produits Microsoft

De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
In libpcap 1.10.6 the function has been reimplemented to apply a stricter input validation and to fail safely if the input is invalid.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
04

Evidence and provenance

Published 31 Dec 2025 · Last source change 2 Jan 2026, 14:38 UTC · CWE-126 · Buffer Over-read

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-205869
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    libpcap-devel as a component of Red Hat Enterprise Linux 10; libpcap.src as a component of Red Hat Enterprise Linux 10; libpcap-devel as a component of Red Hat Enterprise Linux 6; libpcap.src as a component of Red Hat Enterprise Linux 6; libpcap-devel as a component of Red Hat Enterprise Linux 7; libpcap.src as a component of Red Hat Enterprise Linux 7; libpcap as a component of Red Hat Enterprise Linux 8; libpcap-devel as a component of Red Hat Enterprise Linux 8; libpcap.src as a component of Red Hat Enterprise Linux 8; libpcap-devel as a component of Red Hat Enterprise Linux 9; libpcap.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
    After
    libpcap-devel as a component of Red Hat Enterprise Linux 10; libpcap.src as a component of Red Hat Enterprise Linux 10; libpcap-devel as a component of Red Hat Enterprise Linux 6; libpcap.src as a component of Red Hat Enterprise Linux 6; libpcap-devel as a component of Red Hat Enterprise Linux 7; libpcap.src as a component of Red Hat Enterprise Linux 7; libpcap as a component of Red Hat Enterprise Linux 8; libpcap-devel as a component of Red Hat Enterprise Linux 8; libpcap.src as a component of Red Hat Enterprise Linux 8; libpcap-devel as a component of Red Hat Enterprise Linux 9; libpcap.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-11961 · cve.blacktree.nl