CVE-2026-46319— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于act_ct中tcf_ct_flow_table_get()函数在rhashtable_lookup_fast()内部释放RCU读锁后，返回的ct_ft对象可能已被释放，导致释放后重用，可能导致权限提升。
可能的 ATT&CK 技术 1 AI
T1068 · Exploitation for Privilege Escalation影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 138470a9b2cc2e26e6018300394afc3858a54e6a< ece578ca61e572df96cfc80456357ebfae0b4b9e |
affected |
138470a9b2cc2e26e6018300394afc3858a54e6a< a2e0c045c87aa252eb61412e67dd91f2c2b19f81 |
affected | ||
138470a9b2cc2e26e6018300394afc3858a54e6a< 67c9ecc9f2575273ed1323e312881fc98ac83d6d |
affected | ||
138470a9b2cc2e26e6018300394afc3858a54e6a< f23424a0ddadb494d4bd57056a7ca703312d3a7b |
affected | ||
138470a9b2cc2e26e6018300394afc3858a54e6a< 17dfb67cb399b660105d9a8c6100851c0d0cdc70 |
affected | ||
138470a9b2cc2e26e6018300394afc3858a54e6a< 4c727c6967a41b37efe0f26332ca9ec5b74785a3 |
affected | ||
138470a9b2cc2e26e6018300394afc3858a54e6a< 3e20e1b3058e0b94638e7b931c138e840e266724 |
affected | ||
138470a9b2cc2e26e6018300394afc3858a54e6a< f462dca0c8415bf0058d0ffa476354c4476d0f09 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-46319 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net/sched: act_ct: Only release RCU read lock after ct_ft
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net/sched: act_ct: Only release RCU read lock after ct_ft
When looking up a flow table in act_ct in tcf_ct_flow_table_get(),
rhashtable_lookup_fast() internally opens and closes an RCU read critical
section before returning ct_ft.
The tcf_ct_flow_table_cleanup_work() can complete before refcount_inc_not_zero()
is invoked on the returned ct_ft resulting in a UAF on the already freed ct_ft
object. This vulnerability can lead to privilege escalation.
Analysis from zdi-disclosures@trendmicro.com:
When initializing act_ct, tcf_ct_init() is called, which internally triggers
tcf_ct_flow_table_get().
static int tcf_ct_flow_table_get(struct net *net, struct tcf_ct_params *params)
{
struct zones_ht_key key = { .net = net, .zone = params->zone };
struct tcf_ct_flow_table *ct_ft;
int err = -ENOMEM;
mutex_lock(&zones_mutex);
ct_ft = rhashtable_lookup_fast(&zones_ht, &key, zones_params); // [1]
if (ct_ft && refcount_inc_not_zero(&ct_ft->ref)) // [2]
goto out_unlock;
...
}
static __always_inline void *rhashtable_lookup_fast(
struct rhashtable *ht, const void *key,
const struct rhashtable_params params)
{
void *obj;
rcu_read_lock();
obj = rhashtable_lookup(ht, key, params);
rcu_read_unlock();
return obj;
}
At [1], rhashtable_lookup_fast() looks up and returns the corresponding ct_ft
from zones_ht . The lookup is performed within an RCU read critical section
through rcu_read_lock() / rcu_read_unlock(), which prevents the object from
being freed. However, at the point of function return, rcu_read_unlock() has
already been called, and there is nothing preventing ct_ft from being freed
before reaching refcount_inc_not_zero(&ct_ft->ref) at [2]. This interval becomes
the race window, during which ct_ft can be freed.
Free Process:
tcf_ct_flow_table_put() is executed through the path tcf_ct_cleanup() call_rcu()
tcf_ct_params_free_rcu() tcf_ct_params_free() tcf_ct_flow_table_put().
static void tcf_ct_flow_table_put(struct tcf_ct_flow_table *ct_ft)
{
if (refcount_dec_and_test(&ct_ft->ref)) {
rhashtable_remove_fast(&zones_ht, &ct_ft->node, zones_params);
INIT_RCU_WORK(&ct_ft->rwork, tcf_ct_flow_table_cleanup_work); // [3]
queue_rcu_work(act_ct_wq, &ct_ft->rwork);
}
}
At [3], tcf_ct_flow_table_cleanup_work() is scheduled as RCU work
static void tcf_ct_flow_table_cleanup_work(struct work_struct *work)
{
struct tcf_ct_flow_table *ct_ft;
struct flow_block *block;
ct_ft = container_of(to_rcu_work(work), struct tcf_ct_flow_table,
rwork);
nf_flow_table_free(&ct_ft->nf_ft);
block = &ct_ft->nf_ft.flow_block;
down_write(&ct_ft->nf_ft.flow_block_lock);
WARN_ON(!list_empty(&block->cb_list));
up_write(&ct_ft->nf_ft.flow_block_lock);
kfree(ct_ft); // [4]
module_put(THIS_MODULE);
}
tcf_ct_flow_table_cleanup_work() frees ct_ft at [4]. When this function executes
between [1] and [2], UAF occurs.
This race condition has a very short race window, making it generally
difficult to trigger. Therefore, to trigger the vulnerability an msleep(100) was
inserted after[1]
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于act_ct中tcf_ct_flow_table_get()函数在rhashtable_lookup_fast()内部释放RCU读锁后，返回的ct_ft对象可能已被释放，导致释放后重用，可能导致权限提升。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-46319 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-46319 的情报信息
请登录查看更多情报信息。
CVE-2026-46319 补丁与修复 (8)
同批安全公告 · Linux · 2026-06-09 · 共 21 条
| CVE-2026-46325 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-46316 | 9.3 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-46317 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46326 | 8.4 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46332 | 8.0 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-52907 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46323 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46330 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46324 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46327 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-52906 | 7.7 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46320 | 7.4 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46328 | 7.3 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46322 | 7.1 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46321 | 7.1 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46329 | Linux kernel 安全漏洞 | |
| CVE-2026-46318 | Linux kernel 安全漏洞 | |
| CVE-2026-52904 | Linux kernel 安全漏洞 | |
| CVE-2026-52905 | Linux kernel 安全漏洞 | |
| CVE-2026-46315 | Linux kernel 安全漏洞 |
IV. Related Vulnerabilities
V. Comments for CVE-2026-46319
暂无评论