LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50755: udf: Avoid double brelse() in udf_rename()

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> 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50755 is a Linux kernel UDF filesystem bug. Under certain rename error handling, the kernel may release the same buffer twice, triggering a warning about freeing an already free buffer. Public sources do not provide CVSS, confirmed impact beyond the warning, or evidence of active exploitation.

Executive priority

Track and remediate through normal kernel update processes. Raise priority for environments that handle untrusted media or disk images. Current public evidence does not justify emergency response absent vendor-specific severity or exploitation reports.

Technical view

The issue is in fs/udf udf_rename(). When udf_find_entry() returns NULL, it already releases ofibh.sbh and ofibh.ebh; udf_rename() released them again, unbalancing buffer_head b_count. The kernel fix avoids brelse() in udf_rename() on that failure path.

Likely exposure

Systems running affected Linux kernel versions with UDF filesystem support are potentially exposed, especially where UDF media or images can be mounted or processed. The source lists Linux kernel versions from 4.2 through 6.2 as affected, but distribution-specific package status is not provided.

Exploitation context

The report came from syzbot and shows a kernel warning during cleanup after UDF rename handling. The provided sources do not state remote exploitability, privilege requirements, denial-of-service impact, or active exploitation. KEV status is false.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. No CWE, CVSS, or exploitability assessment is provided. The affected-version data appears broad and should be reconciled against distro backports and stable commit inclusion.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2022-50755 status.
  • Update to a kernel package containing the referenced stable UDF fix.
  • If UDF is unnecessary, consider disabling or restricting UDF mounting per vendor guidance.
  • Prioritize systems that mount untrusted removable media or disk images.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Check whether UDF filesystem support is enabled or loadable.
  • Map installed kernels to vendor advisories or the referenced stable commits.
  • Review logs for related kernel warnings mentioning brelse or UDF rename.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50755 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31, 231473f6ddcef9c01993e0bfe36acc6f8e425c31unaffected
LinuxLinux4.2, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.