https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 01 Nov 2026 22:47:21 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98811 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/sched: cls_api: reclaim an empty proto on the error path</p> <p>Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner&#39;s tcf_chain_tp_delete_empty() attempt gives up because the loser&#39;s handle is still in the idr, and the loser&#39;s error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.</p> <p>Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.</p> <p>This is a follow-up to commit d4e359b3608a (&#34;net/sched: cls_api: fix teardown of an adopted proto on insert-race loss&#34;), which stopped the loser of the insert race from unlinking the winner&#39;s live proto but left the empty-proto residual in place.</p> <p>Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; v…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/sched: cls_api: reclaim an empty proto on the error path</p> <p>Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner&#39;s tcf_chain_tp_delete_empty() attempt gives up because the loser&#39;s handle is still in the idr, and the loser&#39;s error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.</p> <p>Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.</p> <p>This is a follow-up to commit d4e359b3608a (&#34;net/sched: cls_api: fix teardown of an adopted proto on insert-race loss&#34;), which stopped the loser of the insert race from unlinking the winner&#39;s live proto but left the empty-proto residual in place.</p> <p>Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; v…</p> https://db.gcve.eu/vuln/fkie_cve-2026-98811 https://db.gcve.eu/vuln/ghsa-8rvg-cc82-cvp9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/sched: cls_api: reclaim an empty proto on the error path</p> <p>Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner&#39;s tcf_chain_tp_delete_empty() attempt gives up because the loser&#39;s handle is still in the idr, and the loser&#39;s error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.</p> <p>Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.</p> <p>This is a follow-up to commit d4e359b3608a (&#34;net/sched: cls_api: fix teardown of an adopted proto on insert-race loss&#34;), which stopped the loser of the insert race from unlinking the winner&#39;s live proto but left the empty-proto residual in place.</p> <p>Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; v…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/sched: cls_api: reclaim an empty proto on the error path</p> <p>Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner&#39;s tcf_chain_tp_delete_empty() attempt gives up because the loser&#39;s handle is still in the idr, and the loser&#39;s error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.</p> <p>Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.</p> <p>This is a follow-up to commit d4e359b3608a (&#34;net/sched: cls_api: fix teardown of an adopted proto on insert-race loss&#34;), which stopped the loser of the insert race from unlinking the winner&#39;s live proto but left the empty-proto residual in place.</p> <p>Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; v…</p> https://db.gcve.eu/vuln/ghsa-8rvg-cc82-cvp9 https://db.gcve.eu/vuln/msrc_cve-2026-98811 msrc_CVE-2026-98811 https://db.gcve.eu/vuln/msrc_cve-2026-98811 https://db.gcve.eu/vuln/ubuntu-cve-2026-98811 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: reclaim an empty proto on the error path Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner&#39;s tcf_chain_tp_delete_empty() attempt gives up because the loser&#39;s handle is still in the idr, and the loser&#39;s error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down. Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them. This is a follow-up to commit d4e359b3608a (&#34;net/sched: cls_api: fix teardown of an adopted proto on insert-race loss&#34;), which stopped the loser of the insert race from unlinking the winner&#39;s live proto but left the empty-proto residual in place. Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth p…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: reclaim an empty proto on the error path Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner&#39;s tcf_chain_tp_delete_empty() attempt gives up because the loser&#39;s handle is still in the idr, and the loser&#39;s error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down. Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them. This is a follow-up to commit d4e359b3608a (&#34;net/sched: cls_api: fix teardown of an adopted proto on insert-race loss&#34;), which stopped the loser of the insert race from unlinking the winner&#39;s live proto but left the empty-proto residual in place. Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth p…</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98811