CVE-2026-68156

Unknown

Last modified

CVE-2026-68156 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: libceph: refresh auth->authorizer_buf{,_len} after authorizer update ceph_x_create_authorizer() caches au->buf->vec.iov_base and au->buf->vec.iov_len in struct ceph_auth_handshake. These cached values are then used by the messenger connect code when sending the authorizer. ceph_x_update_authorizer() can rebuild the authorizer when a newer service ticket is available.

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: refresh auth->authorizer_buf{,_len} after authorizer update ceph_x_create_authorizer() caches au->buf->vec.iov_base and au->buf->vec.iov_len in struct ceph_auth_handshake. These cached values are then used by the messenger connect code when sending the authorizer. ceph_x_update_authorizer() can rebuild the authorizer when a newer service ticket is available. If the rebuilt authorizer no longer fits in the existing buffer, ceph_x_build_authorizer() drops its reference to au->buf and allocates a new one. If this is the final reference, ceph_buffer_put() frees the old ceph_buffer and its vec.iov_base, but auth->authorizer_buf still points at that freed memory. A subsequent msgr1 reconnect can therefore queue the stale pointer and trigger a KASAN slab-use-after-free in _copy_from_iter() while tcp_sendmsg() copies the authorizer. Refresh auth->authorizer_buf and auth->authorizer_buf_len after a successful authorizer rebuild so the messenger sends the current buffer.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 0bed9b5c523d577378b6f83eab5835fe30c27208, < 9d37aec9ffe4e743dabc3f84502e9723e17a30d4; >= 0bed9b5c523d577378b6f83eab5835fe30c27208, < 75e82e8944ac1efe9fdb88bd2f14d9a031282bdf; >= 0bed9b5c523d577378b6f83eab5835fe30c27208, < 0060ec912292a550198d8d18ac95b433c92a7091; >= 0bed9b5c523d577378b6f83eab5835fe30c27208, < 5ecfcd5c05866f185357700b81b461dae4f5ebb2; >= 0bed9b5c523d577378b6f83eab5835fe30c27208, < 937d61f86d377a3aa578adae7a3dfcecdddf9d89; 29c65a277a64645af853e8c9a9b3dda0ddc421e0; d2c7223497cf8228416c70e3f4238ddd6c5bdf3c; >= 3.4.50, < 3.5; >= 3.9.7, < 3.10
LinuxLinux3.10

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68156?
In the Linux kernel, the following vulnerability has been resolved: libceph: refresh auth->authorizer_buf{,_len} after authorizer update ceph_x_create_authorizer() caches au->buf->vec.iov_base and au->buf->vec.iov_len in struct ceph_auth_handshake. These cached values are then used by the messenger connect code when sending the authorizer. ceph_x_update_authorizer() can rebuild the authorizer when a newer service ticket is available. If the rebuilt authorizer no longer fits in the existing buffer, ceph_x_build_authorizer() drops its reference to au->buf and allocates a new one. If this is the final reference, ceph_buffer_put() frees the old ceph_buffer and its vec.iov_base, but auth->authorizer_buf still points at that freed memory. A subsequent msgr1 reconnect can therefore queue the stale pointer and trigger a KASAN slab-use-after-free in _copy_from_iter() while tcp_sendmsg() copies the authorizer. Refresh auth->authorizer_buf and auth->authorizer_buf_len after a successful authorizer rebuild so the messenger sends the current buffer.
How severe is CVE-2026-68156?
Severity scoring for CVE-2026-68156 is pending analysis.
How do I fix CVE-2026-68156?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68156?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST