CVE-2022-50755

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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:

udf: Avoid double brelse() in udf_rename()

syzbot reported a warning like below [1]:

VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ? generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ? smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ? __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80 blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760 deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0 task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ? reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ? rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0 __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The cause of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes unbalanced.

This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry() returns NULL.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (9)

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

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

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

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

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

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

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

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d2cad69547abea961fa80426d600b861de1952b
generic

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78eba2778ae10fb2a9d450e14d26eb6f6bf1f906
generic

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fca09045509f5bde8fc28e68fbca38cb4bdcf2e
generic

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40dba68d418237b1ae2beaa06d46a94dd946278e
generic

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/156d440dea97deada629bb51cb17887abd862605
generic

udf: Avoid double brelse() in udf_rename() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/090bf49833c51da297ec74f98ad2bf44daea9311

Vendor Advisories for CVE-2022-50755(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.337—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 (25 versions)5.10.178-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—

Data Freshness Timeline

(refreshed 3× in last 7d / 23× 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 202 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-50755?
CVE-2022-50755 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 brelse+0x67/0xa0 ... Call Trace: <TASK>…
When was CVE-2022-50755 disclosed?
CVE-2022-50755 was first published in the National Vulnerability Database on December 24, 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-50755 actively exploited?
CVE-2022-50755 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 88.6% of all scored CVEs.
What is the CVSS score of CVE-2022-50755?
CVE-2022-50755 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50755?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50755, 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-50755

Explore →

Is Your Infrastructure Affected by CVE-2022-50755?

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

Start Free Scan →Browse All CVEs