CVE-2026-76890

Description

A flaw was found in Wireshark's sharkd component. A remote attacker could exploit an expired pointer dereference, which leads to a crash in the sharkd service. This vulnerability could result in a denial of service (DoS) for affected systems, requiring user interaction to trigger the flaw.

Statement

This Low impact denial of service vulnerability in Wireshark's sharkd component requires high attack complexity and user interaction for successful exploitation. The limited exposure and specific conditions needed to trigger the flaw reduce its overall risk to Red Hat supported products.

Mitigation

To mitigate this denial of service vulnerability, ensure the `sharkd` service is not running if its functionality is not required. If `sharkd` is necessary, restrict network access to trusted hosts using firewall rules to limit exposure. This may impact remote analysis capabilities if `sharkd` is actively used. A service restart or reload may be required for changes to take effect.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score3.16.53.1
Attack VectorNetworkNetworkNetwork
Attack ComplexityHighLowHigh
Privileges RequiredNoneNoneNone
User InteractionRequiredRequiredRequired
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneNone
Integrity ImpactNoneNoneNone
Availability ImpactLowHighLow

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.