CVE-2022-48847

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-07-16. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

watch_queue: Fix filter limit check

In watch_queue_set_filter(), there are a couple of places where we check that the filter type value does not exceed what the type_filter bitmap can hold. One place calculates the number of bits by:

if (tf[i].type >= sizeof(wfilter->type_filter) * 8)

which is fine, but the second does:

if (tf[i].type >= sizeof(wfilter->type_filter) * BITS_PER_LONG)

which is not. This can lead to a couple of out-of-bounds writes due to a too-large type:

(1) __set_bit() on wfilter->type_filter (2) Writing more elements in wfilter->filters[] than we allocated.

Fix this by just using the proper WATCH_TYPE__NR instead, which is the number of types we actually know about.

The bug may cause an oops looking something like:

BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740 Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611 ... Call Trace: dump_stack_lvl+0x45/0x59 print_address_description.constprop.0+0x1f/0x150 ... kasan_report.cold+0x7f/0x11b ... watch_queue_set_filter+0x659/0x740 ... __x64_sys_ioctl+0x127/0x190 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae

Allocated by task 611: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x81/0xa0 watch_queue_set_filter+0x23a/0x740 __x64_sys_ioctl+0x127/0x190 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae

The buggy address belongs to the object at ffff88800d2c66a0 which belongs to the cache kmalloc-32 of size 32 The buggy address is located 28 bytes inside of 32-byte region [ffff88800d2c66a0, ffff88800d2c66c0)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 16, 2024

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

watch_queue: Fix filter limit check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c993ee0f9f81caf5767a50d1faeba39a0dc82af2
generic

watch_queue: Fix filter limit check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b36588ebbcef74583824c08352e75838d6fb4ff2
generic

watch_queue: Fix filter limit check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b09f28f70a5046acd64138075ae3f095238b045
generic

watch_queue: Fix filter limit check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/648895da69ced90ca770fd941c3d9479a9d72c16

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.106—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-08-07 16:24 UTCEPSS rescore
  2. 2026-08-06 13:44 UTCEPSS rescore
  3. 2026-08-05 19:15 UTCEPSS rescore
  4. 2026-08-05 09:37 UTCEG score recompute
  5. 2026-08-05 09:37 UTCGHSA enrichment
  6. 2026-08-04 15:07 UTCEPSS rescore
  7. 2026-08-04 12:00 UTCEG score recompute
  8. 2026-08-04 11:59 UTCGHSA enrichment
  9. 2026-08-04 10:35 UTCEPSS rescore
  10. 2026-08-04 09:48 UTCEG score recompute
  11. 2026-08-04 09:48 UTCGHSA enrichment
  12. 2026-08-03 10:33 UTCEPSS rescore
  13. 2026-08-02 02:24 UTCEPSS rescore
  14. 2026-08-01 04:13 UTCEPSS rescore
  15. 2026-08-01 04:13 UTCEPSS rescore
  16. 2026-07-31 19:12 UTCOSV refresh
  17. 2026-07-30 16:25 UTCEPSS rescore
  18. 2026-07-30 01:28 UTCEPSS rescore
  19. 2026-07-28 15:34 UTCEPSS rescore
  20. 2026-07-26 14:52 UTCEPSS rescore
  21. 2026-07-26 14:52 UTCEPSS rescore
  22. 2026-07-25 14:16 UTCEPSS rescore
  23. 2026-07-24 14:15 UTCEPSS rescore
  24. 2026-07-23 14:16 UTCEPSS rescore
  25. 2026-07-23 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 02:16 UTCEG score recompute
  2. 2026-07-22 23:03 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-20 17:05 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 14:29 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-19 02:27 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-16 17:00 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-15 01:58 UTCEPSS rescore
  18. 2026-07-15 01:58 UTCEPSS rescore
  19. 2026-07-14 02:25 UTCOSV refresh
  20. 2026-07-13 22:28 UTCEPSS rescore
  21. 2026-07-13 22:28 UTCEPSS rescore
  22. 2026-07-13 06:11 UTCEPSS rescore
  23. 2026-07-13 06:11 UTCEPSS rescore
  24. 2026-07-12 05:44 UTCEPSS rescore
  25. 2026-07-11 08:25 UTCEPSS rescore
  26. 2026-07-11 08:25 UTCEPSS rescore
  27. 2026-07-09 19:08 UTCEPSS rescore
  28. 2026-07-08 15:13 UTCEPSS rescore
  29. 2026-07-07 13:44 UTCEPSS rescore
  30. 2026-07-06 16:25 UTCEPSS rescore
  31. 2026-07-06 02:21 UTCEPSS rescore
  32. 2026-07-05 02:28 UTCEPSS rescore
  33. 2026-07-04 06:29 UTCEPSS rescore
  34. 2026-07-01 15:04 UTCEPSS rescore
  35. 2026-06-30 23:21 UTCEPSS rescore
  36. 2026-06-30 23:20 UTCEPSS rescore
  37. 2026-06-29 14:04 UTCEPSS rescore
  38. 2026-06-28 14:06 UTCEPSS rescore
  39. 2026-06-28 04:54 UTCEPSS rescore
  40. 2026-06-28 04:54 UTCEPSS rescore
  41. 2026-06-27 03:07 UTCEPSS rescore
  42. 2026-06-27 03:07 UTCEPSS rescore
  43. 2026-06-25 23:46 UTCOSV refresh
  44. 2026-06-25 13:48 UTCEPSS rescore
  45. 2026-06-25 13:48 UTCEPSS rescore
  46. 2026-06-24 14:03 UTCEPSS rescore
  47. 2026-06-24 14:03 UTCEPSS rescore
  48. 2026-06-23 21:31 UTCEPSS rescore
  49. 2026-06-23 21:31 UTCEPSS rescore
  50. 2026-06-22 14:24 UTCEPSS rescore
  51. 2026-06-21 14:55 UTCEPSS rescore
  52. 2026-06-21 14:55 UTCEPSS rescore
  53. 2026-06-21 01:58 UTCEPSS rescore
  54. 2026-06-21 01:58 UTCEPSS rescore
  55. 2026-06-19 19:24 UTCEPSS rescore
  56. 2026-06-19 19:24 UTCEPSS rescore
  57. 2026-06-18 17:51 UTCEPSS rescore
  58. 2026-06-18 17:51 UTCEPSS rescore
  59. 2026-06-17 17:51 UTCEPSS rescore
  60. 2026-06-17 17:51 UTCEPSS rescore
  61. 2026-06-16 17:51 UTCEPSS rescore
  62. 2026-06-16 17:51 UTCEPSS rescore
  63. 2026-06-15 17:47 UTCEPSS rescore
  64. 2026-06-14 23:16 UTCEPSS rescore
  65. 2026-06-12 23:10 UTCEPSS rescore
  66. 2026-06-12 23:10 UTCEPSS rescore
  67. 2026-06-11 13:58 UTCEPSS rescore
  68. 2026-06-11 13:58 UTCEPSS rescore
  69. 2026-06-10 13:21 UTCEPSS rescore
  70. 2026-06-10 13:21 UTCEPSS rescore
  71. 2026-06-08 14:15 UTCEPSS rescore
  72. 2026-06-08 14:15 UTCEPSS rescore
  73. 2026-06-08 12:42 UTCOSV refresh
  74. 2026-06-07 15:23 UTCEPSS rescore
  75. 2026-06-07 15:23 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-48847?
CVE-2022-48847 is a high vulnerability published on July 16, 2024. In the Linux kernel, the following vulnerability has been resolved: watch_queue: Fix filter limit check In watchqueueset_filter(), there are a couple of places where we check that the filter type value does not exceed what the type_filter bitmap can hold. One place calculates the number of bits by:…
When was CVE-2022-48847 disclosed?
CVE-2022-48847 was first published in the National Vulnerability Database on July 16, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-48847 actively exploited?
CVE-2022-48847 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.1% of all scored CVEs.
What is the CVSS score of CVE-2022-48847?
CVE-2022-48847 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-48847?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-48847, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-48847

Explore →

Is Your Infrastructure Affected by CVE-2022-48847?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs