Menu

Star on GitHub · 3.2k

CVE-2022-50749

In the Linux kernel, the following vulnerability has been resolved: acct: fix potential integer overflow in encode_comp_t() The integer overflow is descripted with following codes: > 317 static…

Published Dec 24, 2025EPSS 0.28%

Overview

CVE-2022-50749 is a known-severity vulnerability. It was published on December 24, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

acct: fix potential integer overflow in encode_comp_t()

The integer overflow is descripted with following codes:

> 317 static comp_t encode_comp_t(u64 value)

> 318 {

> 319 int exp, rnd;

......

> 341 exp <<= MANTSIZE;

> 342 exp += value;

> 343 return exp;

> 344 }

Currently comp_t is defined as type of '__u16', but the variable 'exp' is

type of 'int', so overflow would happen when variable 'exp' in line 343 is

greater than 65535.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50749?

CVE-2022-50749 is a known-severity vulnerability. It was published on December 24, 2025.

How severe is CVE-2022-50749?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50749?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50749?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50749 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.