SECUFOCUSNOW
Home›CVE index›CVE-2022-50755
Review reviewHigh

CVE-2022-50755

Linux

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

CVSS
7.8
EPSS
0.18%
8.07% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.18%
Technical severityCVSS 7.8

Vulnerability overview

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

Affected product and versions

Product
Linux
Affected versions
>= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < 78eba2778ae10fb2a9d450e14d26eb6f6bf1f906, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < 9d2cad69547abea961fa80426d600b861de1952b, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < d6da7ec0f94f5208c848e0e94b70f54a0bd9c587, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < 156d440dea97deada629bb51cb17887abd862605, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < 40dba68d418237b1ae2beaa06d46a94dd946278e, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < e7a6a53c871460727be09f4414ccb29fb8697526, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < 4fca09045509f5bde8fc28e68fbca38cb4bdcf2e, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < 090bf49833c51da297ec74f98ad2bf44daea9311, >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31 < c791730f2554a9ebb8f18df9368dc27d4ebc38c2, >= 4.2
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2022-50755 — Linux | SECUFOCUS NOW