CVE-2026-99429

In the Linux kernel, the following vulnerability has been resolved: ocfs2: pin refcount trees before dropping the lookup lock A refcount tree returned to ocfs2_lock_refcount_tree() must stay alive until that caller releases its operation reference. However, ocfs2_get_refcount_tree() returns the cached pointer after dropping osb_lock, and the caller only takes its kref afterwards. The registry reference does not protect this gap from concurrent removal. This can happen when another node frees a refcount root and reuses its block with a different generation while this mount retains the old cached tree. Two local operations on different inodes sharing the new root, such as data CoW and an external xattr update, can then look up the same stale tree. Their inode locks are independent, and both the REFCOUNT DLM lock and rf_sem are acquired after the first operation reference. The following ordering is possible, with no other operation references: Data CoW Xattr update -------- ------------ Look up the old tree under osb_lock, then drop osb_lock Look up the same tree and take a kref Acquire the tree locks and read the new on-disk generation Erase the old tree under osb_lock Unlock and drop the operation kref Drop the registry kref, freeing tree Take a kref through the freed tree pointer The final kref_get() accesses freed rf_getcnt storage, and subsequent accesses in ocfs2_lock_refcount_tree() also use the freed allocation. Take the operation reference in ocfs2_get_refcount_tree() before releasing osb_lock, including when an insertion loses to another lookup. Removal must acquire the same lock, so it cannot drop the registry reference before the lookup has pinned the tree. Keep the existing unlock and error path puts. The two callers that already hold the refcount tree lock keep their borrowed lookup behavior and do not acquire an extra reference. KASAN report as below: BUG: KASAN: slab-use-after-free in ocfs2_lock_refcount_tree+0x94a/0x9b0 Read of size 4 at addr ffff888117212820 by task python3/497 [Kernel and hardware identification omitted.] Call Trace: <TASK> dump_stack_lvl+0x93/0xd0 print_report+0xce/0x630 ? ocfs2_lock_refcount_tree+0x94a/0x9b0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20e/0x420 ? ocfs2_lock_refcount_tree+0x94a/0x9b0 kasan_report+0xe0/0x110 ? ocfs2_lock_refcount_tree+0x94a/0x9b0 ocfs2_lock_refcount_tree+0x94a/0x9b0 ? __pfx_ocfs2_lock_refcount_tree+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? ocfs2_refcount_cow+0x3b6/0xd90 ? srso_alias_return_thunk+0x5/0xfbef5 ? __kmalloc_cache_noprof+0x28d/0x610 ? ocfs2_refcount_cow+0x3b6/0xd90 ocfs2_refcount_cow+0x410/0xd90 ? __pfx_ocfs2_refcount_cow+0x10/0x10 ? __pfx___might_resched+0x10/0x10 ? down_write+0x11a/0x1f0 ? __pfx_down_write+0x10/0x10 ? ocfs2_inode_unlock+0x1a9/0x260 ? __pfx_ocfs2_inode_unlock+0x10/0x10 ? ocfs2_file_write_iter+0x1413/0x1d30 ocfs2_file_write_iter+0x157b/0x1d30 ? __pfx_ocfs2_file_write_iter+0x10/0x10 ? lock_acquire+0x190/0x300 ? __x64_sys_pwrite64+0x1b7/0x220 ? __pfx___might_resched+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? security_file_permission+0x26/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? lock_is_held_type+0x8f/0x100 vfs_write+0x639/0x1010 ? __pfx_ocfs2_file_write_iter+0x10/0x10 ? lock_vma_under_rcu+0x154/0x4a0 ? __pfx_vfs_write+0x10/0x10 ? lock_release+0x121/0x290 ? srso_alias_return_thunk+0x5/0xfbef5 __x64_sys_pwrite64+0x1b7/0x220 ? __pfx___x64_sys_pwrite64+0x10/0x10 ? irqentry_exit+0xbe/0x820 ---truncated---

Score
CVSS 3.1 7.8 High
Status
Received - 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Published
2026-11-19
Last modified
2026-11-22

Affected products

References


Your early warning system for new security vulnerabilities


Open BETA

Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?

Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?

As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.

100+ new CVEs per day

Most CVEs are irrelevant to your infrastructure

Time-to-exploit < 5 days

Attackers are exploiting vulnerabilities faster than ever before

Manual research is time-consuming

Vendor websites, RSS feeds, and blogs need to be searched daily

Vulnerability scanners are lagging behind

Plugin development isn't progressing fast enough to identify risks in a timely manner

CVE Alarm provides you with immediate notifications of relevant security vulnerabilities

CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.

Real-time notification

Direct email notification without delay

Product-based filters

Only CVEs that actually affect your infrastructure

Custom criteria

Filter by CVSS-Score, exposure, products, and vendors

Team-oriented & multi-tenant capable

Assign products or alerts to specific teams or customers

More time to act

Administrators can review and install updates faster

Time savings

No more manually reviewing the flood of new CVE information

Three steps for better patch planning

With CVE Alarm you will easily receive relevant security alerts for your infrastructure.

Subscribe To
Products

Select the IT products you use. From Apache to VMware – all critical assets are monitored.

Define
Criteria

Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.

Get
Notified

Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.

Be faster
than the attackers

With CVE information, you have more time for patch planning and can close security gaps before they are exploited.

Designed for the target group companies and service providers

Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.

Companies with their own IT infrastructure

Medium-sized to large companies that need to proactively monitor their vulnerabilities

Administrators

IT professionals responsible for infrastructure security and maintenance

Security teams and cybersecurity experts

Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures

Chief Information Security Officers (CISOs) & IT managers

Decision-makers who need an overview of critical vulnerabilities

Security service providers

Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs

From experience to innovation. About us and CVE Alarm.

CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.

AVABIS GmbH – Who are we?
We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.

CVE Alarm – How did the idea come about?
In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.

This made us realize that the real problem is not a lack of information, but rather an overabundance of it.

This led to the idea of ​​developing a product that enables companies to manage this information overload and maintain control over their IT security.

Developed and operated in Germany
Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.

Get in contact with our team

Do you have questions about CVE Alarm or would you like a personal consultation?
We're happy to help.

Please use our contact form.