
RaritanのIP-PDU「PX3-5138JR」の最新ファームウェアが9/29付でリリースされていたので適用してみた(4.3.14.5-52917→4.3.15.5-53139)。 リリースノートにはCVE5件対応(CVE-2026-68402/CVE-2026-68118/CVE-2026-68136/CVE-2026-63913/CVE-2026-64554)とLinux Kernel更新(v6.6.155)、ルートシェル上のバグ修正との記載あり。
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
In the Linux kernel, the following vulnerability has been resolved: net: gro: fix double aggregation of flush-marked skbs Commit 0ab03f353d36 ("net-gro: Fix GRO flush when receiving a GSO packet.") added a flush check to skb_gro_receive(), but skb_gro_receive_list() lacks the same validation. As a result, packets marked with NAPI_GRO_CB(skb)->flush may still be re-aggregated. This allows already-GRO'd packets with existing frag_list to be re-aggregated into a new GRO session, corrupting the frag_list chain structure. When skb_segment() attempts to unpack these malformed packets, it encounters invalid state and triggers a kernel panic. Scenario (Tethering/Device forwarding): 1. Driver: Generated aggregated packet P1 via LRO with frag_list 2. Dev A: Receives aggregated fraglist packet and flush flag set 3. Dev A: Re-enters GRO, skb_gro_receive_list() is called 4. Missing flush check allows re-aggregation despite flush flag 5. Frag_list chain becomes corrupted (loops or dangling refs) 6. Dev B: TX path calls skb_segment(), crashes on corrupted frag_list Root cause in skb_segment(): The check at line ~4891: if (hsize <= 0 && i >= nfrags && skb_headlen(list_skb) && (skb_headlen(list_skb) == len || sg)) { When frag_list is corrupted by double aggregation, when list_skb is a NULL pointer from skb->next, skb_headlen(list_skb) dereference NULL/corrupted pointers occurs. Call Trace: skb_headlen(NULL skb) skb_segment tcp_gso_segment tcp4_gso_segment inet_gso_segment skb_mac_gso_segment __skb_gso_segment skb_gso_segment validate_xmit_skb validate_xmit_skb_list sch_direct_xmit qdisc_restart __qdisc_run qdisc_run net_tx_action Fix: Add NAPI_GRO_CB(skb)->flush validation to the early-return check in skb_gro_receive_list(), matching the defensive programming pattern of skb_gro_receive().
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE

RaritanのIP-PDU「PX3-5138JR」の最新ファームウェアが9/29付でリリースされていたので適用してみた(4.3.14.5-52917→4.3.15.5-53139)。 リリースノートにはCVE5件対応(CVE-2026-68402/CVE-2026-68118/CVE-2026-68136/CVE-2026-63913/CVE-2026-64554)とLinux Kernel更新(v6.6.155)、ルートシェル上のバグ修正との記載あり。

🐧 Linux 7.2-rc5 plugs a GRO bug that could crash kernels, but the CVE arrives with no fixed distro builds or CVSS score. Patch status: now featuring “check with your vendor.” https://windowsforum.com/security-alerts.84/cve-2026-68136-linux-gro-crash-fix-lands-in-7-2-rc5.442360/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #LinuxSecurity #KernelVulnerabilities #Wsl2 #GroNetworking https://t.co/MVMfDAeFuS
Post summary
CVE‑2026‑68136 is a GRO bug that can crash Linux kernels; a patch has been applied to 7.2‑rc5 and vendors are urged to update, but there is no evidence of active exploitation or fully released distro fixes.