🛡️ AZL-60327 — kernel

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

CVE-2022-49296 affecting package kernel 5.15.200.1-1

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

ceph: fix possible deadlock when holding Fwb to get inline_data

1, mount with wsync.

2, create a file with O_RDWR, and the request was sent to mds.0:

ceph_atomic_open()-->

ceph_mdsc_do_request(openc)

finish_open(file, dentry, ceph_open)-->

ceph_open()-->

ceph_init_file()-->

ceph_init_file_info()-->

ceph_uninline_data()-->

{

...

if (inline_version == 1 || /* initial version, no data */

inline_version == CEPH_INLINE_NONE)

goto out_unlock;

...

}

The inline_version will be 1, which is the initial version for the

new create file. And here the ci->i_inline_version will keep with 1,

it's buggy.

3, buffer write to the file immediately:

ceph_write_iter()-->

ceph_get_caps(file, need=Fw, want=Fb, ...);

generic_perform_write()-->

a_ops->write_begin()-->

ceph_write_begin()-->

netfs_write_begin()-->

netfs_begin_read()-->

netfs_rreq_submit_slice()-->

netfs_read_from_server()-->

rreq->netfs_ops->issue_read()-->

ceph_netfs_issue_read()-->

{

...

if (ci->i_inline_version != CEPH_INLINE_NONE &&

ceph_netfs_issue_op_inline(subreq))

return;

...

}

ceph_put_cap_refs(ci, Fwb);

The ceph_netfs_issue_op_inline() will send a getattr(Fsr) request to

mds.1.

4, then the mds.1 will request the rd lock for CInode::filelock from

the auth mds.0, the mds.0 will do the CInode::filelock state transation

from excl --> sync, but it need to revoke the Fxwb caps back from the

clients.

While the kernel client has aleady held the Fwb caps and waiting for

the getattr(Fsr).

It's deadlock!

URL: https://tracker.ceph.com/issues/55377

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

AZL-60327 is recorded against 1 package.

  • kernel

Timeline and source

Published on 26 February 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-02-26
Updated 2026-08-12
Modified 2026-04-21
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel

Similar Threats

Free Vulnerability Check

Is your site affected by AZL-60327?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-60327 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.