NVD / CVE Program· CNA Linux

CVE-2026-68156: libceph: refresh auth->authorizer_buf{,_len} after authorizer update

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Linux Linux 0060ec912292a550198d8d18ac95b433c92a7091, 2334e9997308305ee4fd508fdfe6086c4150ed60, 26f814187abceee90dbb29a02133adb4786fbb13; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0060ec912292a550198d8d18ac95b433c92a7091, 2334e9997308305ee4fd508fdfe6086c4150ed60, 26f814187abceee90dbb29a02133adb4786fbb13; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: Aug 10, 2026
Updated: Oct 19, 2026
EPSS: 0.6% · 53th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Linux: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 29c65a277a64645af853e8c9a9b3dda0ddc421e0, d2c7223497cf8228416c70e3f4238ddd6c5bdf3c, 3.10affected
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 2334e9997308305ee4fd508fdfe6086c4150ed60affected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 79a273df64238a4ade8b709689a78589f755b8efaffected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 26f814187abceee90dbb29a02133adb4786fbb13affected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 9d37aec9ffe4e743dabc3f84502e9723e17a30d4affected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 75e82e8944ac1efe9fdb88bd2f14d9a031282bdfaffected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 0060ec912292a550198d8d18ac95b433c92a7091affected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 5ecfcd5c05866f185357700b81b461dae4f5ebb2affected · git
- 0bed9b5c523d577378b6f83eab5835fe30c27208 and later · before 937d61f86d377a3aa578adae7a3dfcecdddf9d89affected · git
- 3.4.50 and later · before 3.5affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	bpftool	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-abi-stablelists	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-core	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-cross-headers	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-debug	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-debug-core	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-debug-devel	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-debug-modules	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-debug-modules-extra	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-devel	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-doc	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-headers	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-modules	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-modules-extra	before 4.18.0-553.169.1.el8_10	4.18.0-553.169.1.el8_10
AlmaLinux:8	kernel-rt	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-core	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-debug	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-debug-core	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-debug-devel	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-debug-modules	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-debug-modules-extra	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-devel	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10
AlmaLinux:8	kernel-rt-modules	before 4.18.0-553.169.1.rt7.510.el8_10	4.18.0-553.169.1.rt7.510.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-68154Aug 10, 2026 · libceph: reject zero bucket types in crush_decode
39Monitor
← EarlierCVE-2026-68155Aug 10, 2026 · libceph: Reject monmaps advertising zero monitors
30Monitor
Later →CVE-2026-68157Aug 10, 2026 · libceph: guard missing CRUSH type name lookup
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	0060ec912292a550198d8d18ac95b433c92a7091	Vendor (CNA)
Linux Linux	2334e9997308305ee4fd508fdfe6086c4150ed60	Vendor (CNA)
Linux Linux	26f814187abceee90dbb29a02133adb4786fbb13	Vendor (CNA)
Linux Linux	3.10	Vendor (CNA)
Linux Linux	3.5	Vendor (CNA)
Linux Linux	5ecfcd5c05866f185357700b81b461dae4f5ebb2	Vendor (CNA)
Linux Linux	75e82e8944ac1efe9fdb88bd2f14d9a031282bdf	Vendor (CNA)
Linux Linux	79a273df64238a4ade8b709689a78589f755b8ef	Vendor (CNA)
Linux Linux	937d61f86d377a3aa578adae7a3dfcecdddf9d89	Vendor (CNA)
Linux Linux	9d37aec9ffe4e743dabc3f84502e9723e17a30d4	Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.0	6.6.150.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:kernel	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-core	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug-core	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug-devel	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug-modules	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug-modules-core	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-devel	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
almalinux:kernel-64k-devel-matched	5.14.0-687.50.1.el9_8 · AlmaLinux:9	Package registry (OSV)
debian:linux	6.1.187-1 · Debian:12	Package registry (OSV)
debian:linux-6.12	6.12.101-1~deb12u1 · Debian:12	Package registry (OSV)
red hat:kernel-64k-debug-debuginfo	0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:kernel-64k-debug-devel	0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:kernel-64k-debug-devel-matched	0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:kernel-64k-debuginfo	0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:kernel-64k-devel	0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
39Monitor
CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
39Monitor
CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()
39Monitor
CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification
39Monitor
CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
39Monitor
CVE-2026-720695 days apartlocking/rt: Fix the incorrect RCU protection in rt_spin_unlock()
39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

SSVC exploitation— → noneOct 16, 2026, 5:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0060ec912292a550198d8d18ac95b433c92a7091

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records