nday
CVE-2026-98432

ipv4: free inet_opt and ireq_opt after an RCU grace period

Linux / Linux

CVE 공개 14일 후 PoC 공개. nday가 아직 패치 근거를 수집하지 않았습니다. 패치가 없다는 뜻은 아닙니다. PoC 출처 4곳 중 1곳 등재: github. CISA KEV 미등재.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by NVD's analysts
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
현재 단계
POC
공개
공개 → 기술 분석
T+17d ANA 시점은 날짜 단위
CVSS
9.8 CRITICAL v3.1

생명주기

가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
10-15T12:08Z
PAT패치
아직 기록 없음
ANA분석
10-30T00:21Z 외 4건
POCPoC
10-29, 날짜만 외 20건
ITW악용
아직 기록 없음
KEVKEV
아직 기록 없음

요약

In the Linux kernel, the following vulnerability has been resolved:

ipv4: free inet_opt and ireq_opt after an RCU grace period

tcp_v4_syn_recv_sock() transfers ownership of ireq->ireq_opt to the child socket (newinet->inet_opt) without copying it.

Another cpu can concurrently process a retransmitted SYN for the same request socket, and send a SYNACK from tcp_check_req(). tcp_v4_send_synack() and inet_csk_route_req() read ireq->ireq_opt under rcu_read_lock() only, and ip_build_and_send_pkt() and ip_options_build() then read opt->optlen twice.

Note that the SYNACK timer itself is not an issue: it holds a reference on its request socket, and inet_csk_reqsk_queue_drop() calls timer_delete_sync() before the child can be freed.

Since commit 079096f103fa ("tcp/dccp: install syn_recv requests into ehash table"), request sockets are processed without holding the listener lock, so nothing prevents the child socket from being freed while the SYNACK is still being built. TCP child sockets do not have SOCK_RCU_FREE, and inet_sock_destruct() frees inet_opt with a plain kfree(), leading to a use-after-free in ip_options_build().

A similar issue exists with request socket migration (net.ipv4.tcp_migrate_req=1, or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program). reqsk_timer_handler() clones the request socket with inet_reqsk_clone(), so that the old request socket and its clone share the same ireq_opt, then reqsk_migrate_reset() clears the pointer in the old one. Another cpu holding a reference on the old request socket can still be using these options (sending a SYNACK, or creating a child in tcp_v4_syn_recv_sock()) when the clone is freed, and tcp_v4_reqsk_destructor() also uses a plain kfree().

Readers already use RCU, and other paths replacing inet_opt (do_ip_setsockopt(), cipso_v4_sock_setattr()...) already use kfree_rcu(). Use kfree_rcu() in inet_sock_destruct() and tcp_v4_reqsk_destructor() as well.

IPv6 is not affected by the first issue, because tcp_v6_syn_recv_sock() duplicates the options. tcp_v6_reqsk_destructor() has the same migration issue with ipv6_opt, which is only set by CALIPSO. This will be addressed in a separate patch.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

이벤트 로그

+DISCVE 공개

CVE 레코드 공개(CNA: Linux). CVSS 9.8(치명적).

출처 cvelist · nday 일괄 수집 · 원본
{
  "id": 457727,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-98432",
  "occurred_at": "2026-10-15T12:08:22.205Z",
  "observed_at": "2026-11-13T05:40:20.493151Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 9.8,
      "base_severity": "CRITICAL"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-15T12:08:22.205Z",
    "assigner_short_name": "Linux"
  }
}
2026-10-29출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: Quaerendir/cve-2026-98432-audit. 날짜는 저장소 생성일.

출처 github 1438519697 · nday 일괄 수집 · 원본
{
  "id": 483237,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/Quaerendir/cve-2026-98432-audit",
  "occurred_at": "2026-10-29T14:17:42Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1438519697",
  "detail": {
    "url": "https://github.com/Quaerendir/cve-2026-98432-audit",
    "title": "Quaerendir/cve-2026-98432-audit",
    "precision": "day"
  }
}
2026-10-29출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: nsrg-fmlorg/kpatch-cve-2026-98432. 날짜는 저장소 생성일.

출처 github 1438711740 · nday 일괄 수집 · 원본
{
  "id": 483238,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/nsrg-fmlorg/kpatch-cve-2026-98432",
  "occurred_at": "2026-10-29T16:58:02Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1438711740",
  "detail": {
    "url": "https://github.com/nsrg-fmlorg/kpatch-cve-2026-98432",
    "title": "nsrg-fmlorg/kpatch-cve-2026-98432",
    "precision": "day"
  }
}
2026-10-29출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: typhoon1217/cve-2026-98432-mitigation. 날짜는 저장소 생성일.

출처 github 1438739245 · nday 일괄 수집 · 원본
{
  "id": 483239,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/typhoon1217/cve-2026-98432-mitigation",
  "occurred_at": "2026-10-29T17:22:03Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1438739245",
  "detail": {
    "url": "https://github.com/typhoon1217/cve-2026-98432-mitigation",
    "title": "typhoon1217/cve-2026-98432-mitigation",
    "precision": "day"
  }
}
+ANA기술 분석

oss-security 메일링 리스트에 게시: “Fwd: Protecting against CVE-2026-98432 when using Go programs”.

출처 osssec 2026/q4/437 · nday 실시간 관측 · 원본
{
  "id": 496021,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/437",
  "occurred_at": "2026-10-30T00:21:41Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/437",
  "detail": {
    "list": "oss-security",
    "author": "Alan Coopersmith",
    "subject": "Fwd: Protecting against CVE-2026-98432 when using Go programs",
    "is_reply": false
  }
}
2026-10-30출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: H1z3-br0/CVE-2026-98432. 날짜는 저장소 생성일.

출처 github 1439099519 · nday 일괄 수집 · 원본
{
  "id": 483240,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/H1z3-br0/CVE-2026-98432",
  "occurred_at": "2026-10-30T00:22:53Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1439099519",
  "detail": {
    "url": "https://github.com/H1z3-br0/CVE-2026-98432",
    "title": "H1z3-br0/CVE-2026-98432",
    "precision": "day"
  }
}
2026-10-30출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: mahdi-salmanzade/CVE-2026-98432. 날짜는 저장소 생성일.

출처 github 1439100476 · nday 일괄 수집 · 원본
{
  "id": 483241,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/mahdi-salmanzade/CVE-2026-98432",
  "occurred_at": "2026-10-30T00:24:18Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1439100476",
  "detail": {
    "url": "https://github.com/mahdi-salmanzade/CVE-2026-98432",
    "title": "mahdi-salmanzade/CVE-2026-98432",
    "precision": "day"
  }
}
+ANA기술 분석

oss-security 메일링 리스트의 답글: “Re: Protecting against CVE-2026-98432 when using Go programs”.

출처 osssec 2026/q4/442 · nday 실시간 관측 · 원본
{
  "id": 496025,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/442",
  "occurred_at": "2026-10-30T09:05:46Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/442",
  "detail": {
    "list": "oss-security",
    "author": "John Haxby",
    "subject": "Re: Protecting against CVE-2026-98432 when using Go programs",
    "is_reply": true
  }
}
2026-10-30출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: bitwire-it/Probe-CVE-2026-98432. 날짜는 저장소 생성일.

출처 github 1439549618 · nday 일괄 수집 · 원본
{
  "id": 483242,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/bitwire-it/Probe-CVE-2026-98432",
  "occurred_at": "2026-10-30T09:56:32Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1439549618",
  "detail": {
    "url": "https://github.com/bitwire-it/Probe-CVE-2026-98432",
    "title": "bitwire-it/Probe-CVE-2026-98432",
    "precision": "day"
  }
}
2026-10-30출처 제공, 날짜만
+POC공개 PoC

GitHub PoC 저장소: tc4dy/CVE-2026-98432-PoC-Exploit. 날짜는 저장소 생성일.

출처 github 1439746141 · nday 일괄 수집 · 원본
{
  "id": 483243,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/tc4dy/CVE-2026-98432-PoC-Exploit",
  "occurred_at": "2026-10-30T13:11:26Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": true,
  "dedupe_key": "1439746141",
  "detail": {
    "url": "https://github.com/tc4dy/CVE-2026-98432-PoC-Exploit",
    "title": "tc4dy/CVE-2026-98432-PoC-Exploit",
    "precision": "day"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

연구자 논의

최근 7일간 연구자 1명이 언급

목록의 연구자가 X에서 이 CVE를 언급한 게시물입니다. 원문 그대로 보여 주며 nday는 검증하지 않습니다.

  1. 2026-11-18

    @hardenedlinux의 2026-11-18 게시물입니다. 읽으려면 로그인하세요.

게시물 1건을 읽으려면 로그인하세요.

로그인하고 읽기

Discussion

0 comments

No comments yet.