CVE record · CVE-2022-48939

bpf: Add schedule points in batch ops

No CVSS scoreEPSS 0.0020 · 10th percentile

Published by the CVE Program (CNA: Linux) at 22 Aug 2024, 03:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Linux Linux
  • affected cb4d03ab499d4c040f4ab6fd4389d2b49f42b5a5 to before 7ef94bfb08fb9e73defafbd5ddef6b5a0e2ee12b git
  • affected cb4d03ab499d4c040f4ab6fd4389d2b49f42b5a5 to before 8628f489b749a4f9767991631921dbe3fbcdc784 git
  • affected cb4d03ab499d4c040f4ab6fd4389d2b49f42b5a5 to before 7e8099967d0e3ff9d1ae043e80b27fbe46c08417 git
  • affected cb4d03ab499d4c040f4ab6fd4389d2b49f42b5a5 to before 75134f16e7dd0007aa474b281935c5f42e79f2c8 git
Other versions: unaffected
Linux Linux
  • affected 5.6
  • unaffected before 5.6 semver
  • unaffected 5.10.103 to 5.10.*, inclusive semver
  • unaffected 5.15.26 to 5.15.*, inclusive semver
  • unaffected 5.16.12 to 5.16.*, inclusive semver
  • unaffected 5.17 to *, inclusive original_commit_for_fix
Other versions: affected
Identifiers
CVE-2022-48939
CNA
Linux
Published
22 Aug 2024
Updated
11 May 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.0020, the 10th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 22 Aug 2024. New records show when each source confirmed them.

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.