CVE-2022-49407

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-09-22. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

dlm: fix plock invalid read

This patch fixes an invalid read showed by KASAN. A unlock will allocate a "struct plock_op" and a followed send_op() will append it to a global send_list data structure. In some cases a followed dev_read() moves it to recv_list and dev_write() will cast it to "struct plock_xop" and access fields which are only available in those structures. At this point an invalid read happens by accessing those fields.

To fix this issue the "callback" field is moved to "struct plock_op" to indicate that a cast to "plock_xop" is allowed and does the additional "plock_xop" handling if set.

Example of the KASAN output which showed the invalid read:

[ 2064.296453] ================================================================== [ 2064.304852] BUG: KASAN: slab-out-of-bounds in dev_write+0x52b/0x5a0 [dlm] [ 2064.306491] Read of size 8 at addr ffff88800ef227d8 by task dlm_controld/7484 [ 2064.308168] [ 2064.308575] CPU: 0 PID: 7484 Comm: dlm_controld Kdump: loaded Not tainted 5.14.0+ #9 [ 2064.310292] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2064.311618] Call Trace: [ 2064.312218] dump_stack_lvl+0x56/0x7b [ 2064.313150] print_address_description.constprop.8+0x21/0x150 [ 2064.314578] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.315610] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.316595] kasan_report.cold.14+0x7f/0x11b [ 2064.317674] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.318687] dev_write+0x52b/0x5a0 [dlm] [ 2064.319629] ? dev_read+0x4a0/0x4a0 [dlm] [ 2064.320713] ? bpf_lsm_kernfs_init_security+0x10/0x10 [ 2064.321926] vfs_write+0x17e/0x930 [ 2064.322769] ? __fget_light+0x1aa/0x220 [ 2064.323753] ksys_write+0xf1/0x1c0 [ 2064.324548] ? __ia32_sys_read+0xb0/0xb0 [ 2064.325464] do_syscall_64+0x3a/0x80 [ 2064.326387] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.327606] RIP: 0033:0x7f807e4ba96f [ 2064.328470] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 39 87 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 7c 87 f8 ff 48 [ 2064.332902] RSP: 002b:00007ffd50cfe6e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 [ 2064.334658] RAX: ffffffffffffffda RBX: 000055cc3886eb30 RCX: 00007f807e4ba96f [ 2064.336275] RDX: 0000000000000040 RSI: 00007ffd50cfe7e0 RDI: 0000000000000010 [ 2064.337980] RBP: 00007ffd50cfe7e0 R08: 0000000000000000 R09: 0000000000000001 [ 2064.339560] R10: 000055cc3886eb30 R11: 0000000000000293 R12: 000055cc3886eb80 [ 2064.341237] R13: 000055cc3886eb00 R14: 000055cc3886f590 R15: 0000000000000001 [ 2064.342857] [ 2064.343226] Allocated by task 12438: [ 2064.344057] kasan_save_stack+0x1c/0x40 [ 2064.345079] __kasan_kmalloc+0x84/0xa0 [ 2064.345933] kmem_cache_alloc_trace+0x13b/0x220 [ 2064.346953] dlm_posix_unlock+0xec/0x720 [dlm] [ 2064.348811] do_lock_file_wait.part.32+0xca/0x1d0 [ 2064.351070] fcntl_setlk+0x281/0xbc0 [ 2064.352879] do_fcntl+0x5e4/0xfe0 [ 2064.354657] __x64_sys_fcntl+0x11f/0x170 [ 2064.356550] do_syscall_64+0x3a/0x80 [ 2064.358259] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.360745] [ 2064.361511] Last potentially related work creation: [ 2064.363957] kasan_save_stack+0x1c/0x40 [ 2064.365811] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.368100] call_rcu+0x11b/0xf70 [ 2064.369785] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.372404] receive_from_sock+0x290/0x770 [dlm] [ 2064.374607] process_recv_sockets+0x32/0x40 [dlm] [ 2064.377290] process_one_work+0x9a8/0x16e0 [ 2064.379357] worker_thread+0x87/0xbf0 [ 2064.381188] kthread+0x3ac/0x490 [ 2064.383460] ret_from_fork+0x22/0x30 [ 2064.385588] [ 2064.386518] Second to last potentially related work creation: [ 2064.389219] kasan_save_stack+0x1c/0x40 [ 2064.391043] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.393303] call_rcu+0x11b/0xf70 [ 2064.394885] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.397694] receive_from_sock+0x290/0x770 ---truncated---

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (9)

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

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42252d0d2aa9b94d168241710a761588b3959019
generic

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

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

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56aa8d1fbd02357f3bf81bdfba1cde87ce8402fc
generic

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

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

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/899bc4429174861122f0c236588700a4710c1fec
generic

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49cd9eb7b9a7b88124b31e31f8e539acaf1b3a6d
generic

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a1765adf9855cf0f6d3f7e0eb4b78ca66f70dee
generic

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72f2f68970f9bdc252d59e119b385a6441b0b155
generic

dlm: fix plock invalid read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c55155cc365861044d9e6e80e342693e8805e33

Vendor Advisories for CVE-2022-49407(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:5.14.0-70.136.1.rt21.208.el9_02025-07-02redhat
redhatkernel-0:5.14.0-70.136.1.el9_02025-07-01redhat
linuxKernel @ 4.9.318—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (14 versions)5.10.127-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-49407?
CVE-2022-49407 is a high vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: dlm: fix plock invalid read This patch fixes an invalid read showed by KASAN. A unlock will allocate a "struct plockop" and a followed sendop() will append it to a global sendlist data structure. In some cases a followed devread()…
When was CVE-2022-49407 disclosed?
CVE-2022-49407 was first published in the National Vulnerability Database on February 26, 2025, 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-49407 actively exploited?
CVE-2022-49407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.9% of all scored CVEs.
What is the CVSS score of CVE-2022-49407?
CVE-2022-49407 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2022-49407?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49407, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49407

Explore →

Is Your Infrastructure Affected by CVE-2022-49407?

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

Start Free Scan →Browse All CVEs