{"api_version":"1","generated_at":"2026-08-13T11:48:28+00:00","cve":"CVE-2026-68119","urls":{"html":"https://cve.report/CVE-2026-68119","api":"https://cve.report/api/cve/CVE-2026-68119.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-68119","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-68119"},"summary":{"title":"tcp: initialize standalone TCP-AO response padding","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntcp: initialize standalone TCP-AO response padding\n\ntcp_v4_send_ack() and tcp_v6_send_response() construct standalone TCP\nresponses with TCP-AO options.  The option length carries the actual MAC\nlength, but the TCP header length includes the option rounded up to a\nfour-byte boundary.\n\ntcp_ao_hash_hdr() writes the MAC only.  Thus, when the MAC length is not\nfour-byte aligned, the one to three bytes after the MAC are left\nuninitialized and may be transmitted.  For the normal TCP-AO hashing\nmode, those bytes also have to be initialized before computing the MAC.\n\nInitialize only the alignment padding in the TCP-AO branches, before\nhashing the header.  Use TCPOPT_NOP, as in the normal TCP-AO output path.\nThis avoids adding work to non-AO TCP responses while preserving a valid\nauthenticated header.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-10 13:19:56","updated_at":"2026-08-10 13:19:56"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a859b280441fb02f64ed4037f03d5c0c34a7a595","name":"https://git.kernel.org/stable/c/a859b280441fb02f64ed4037f03d5c0c34a7a595","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bbb7db8c74b0b5d17a695136f0f0806ecd0118f6","name":"https://git.kernel.org/stable/c/bbb7db8c74b0b5d17a695136f0f0806ecd0118f6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fadaff3f66e124c3a62237f9c881819a8ac90309","name":"https://git.kernel.org/stable/c/fadaff3f66e124c3a62237f9c881819a8ac90309","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e1a9d3cc11829c5414a75eb39c704f461936eb24","name":"https://git.kernel.org/stable/c/e1a9d3cc11829c5414a75eb39c704f461936eb24","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-68119","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68119","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected decde2586b34b99684faff1eab41e5c496c27fb6 bbb7db8c74b0b5d17a695136f0f0806ecd0118f6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected decde2586b34b99684faff1eab41e5c496c27fb6 fadaff3f66e124c3a62237f9c881819a8ac90309 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected decde2586b34b99684faff1eab41e5c496c27fb6 a859b280441fb02f64ed4037f03d5c0c34a7a595 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected decde2586b34b99684faff1eab41e5c496c27fb6 e1a9d3cc11829c5414a75eb39c704f461936eb24 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.101 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.42 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.6 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc5 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/ipv4/tcp_ipv4.c","net/ipv6/tcp_ipv6.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bbb7db8c74b0b5d17a695136f0f0806ecd0118f6","status":"affected","version":"decde2586b34b99684faff1eab41e5c496c27fb6","versionType":"git"},{"lessThan":"fadaff3f66e124c3a62237f9c881819a8ac90309","status":"affected","version":"decde2586b34b99684faff1eab41e5c496c27fb6","versionType":"git"},{"lessThan":"a859b280441fb02f64ed4037f03d5c0c34a7a595","status":"affected","version":"decde2586b34b99684faff1eab41e5c496c27fb6","versionType":"git"},{"lessThan":"e1a9d3cc11829c5414a75eb39c704f461936eb24","status":"affected","version":"decde2586b34b99684faff1eab41e5c496c27fb6","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/ipv4/tcp_ipv4.c","net/ipv6/tcp_ipv6.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.101","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.42","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc5","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.101","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.42","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.6","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc5","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntcp: initialize standalone TCP-AO response padding\n\ntcp_v4_send_ack() and tcp_v6_send_response() construct standalone TCP\nresponses with TCP-AO options.  The option length carries the actual MAC\nlength, but the TCP header length includes the option rounded up to a\nfour-byte boundary.\n\ntcp_ao_hash_hdr() writes the MAC only.  Thus, when the MAC length is not\nfour-byte aligned, the one to three bytes after the MAC are left\nuninitialized and may be transmitted.  For the normal TCP-AO hashing\nmode, those bytes also have to be initialized before computing the MAC.\n\nInitialize only the alignment padding in the TCP-AO branches, before\nhashing the header.  Use TCPOPT_NOP, as in the normal TCP-AO output path.\nThis avoids adding work to non-AO TCP responses while preserving a valid\nauthenticated header."}],"providerMetadata":{"dateUpdated":"2026-08-10T11:58:39.026Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bbb7db8c74b0b5d17a695136f0f0806ecd0118f6"},{"url":"https://git.kernel.org/stable/c/fadaff3f66e124c3a62237f9c881819a8ac90309"},{"url":"https://git.kernel.org/stable/c/a859b280441fb02f64ed4037f03d5c0c34a7a595"},{"url":"https://git.kernel.org/stable/c/e1a9d3cc11829c5414a75eb39c704f461936eb24"}],"title":"tcp: initialize standalone TCP-AO response padding","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-68119","datePublished":"2026-08-10T11:58:39.026Z","dateReserved":"2026-07-30T09:28:09.369Z","dateUpdated":"2026-08-10T11:58:39.026Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-10 13:19:56","lastModifiedDate":"2026-08-10 13:19:56","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"68119","Ordinal":"1","Title":"tcp: initialize standalone TCP-AO response padding","CVE":"CVE-2026-68119","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"68119","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntcp: initialize standalone TCP-AO response padding\n\ntcp_v4_send_ack() and tcp_v6_send_response() construct standalone TCP\nresponses with TCP-AO options.  The option length carries the actual MAC\nlength, but the TCP header length includes the option rounded up to a\nfour-byte boundary.\n\ntcp_ao_hash_hdr() writes the MAC only.  Thus, when the MAC length is not\nfour-byte aligned, the one to three bytes after the MAC are left\nuninitialized and may be transmitted.  For the normal TCP-AO hashing\nmode, those bytes also have to be initialized before computing the MAC.\n\nInitialize only the alignment padding in the TCP-AO branches, before\nhashing the header.  Use TCPOPT_NOP, as in the normal TCP-AO output path.\nThis avoids adding work to non-AO TCP responses while preserving a valid\nauthenticated header.","Type":"Description","Title":"tcp: initialize standalone TCP-AO response padding"}]}}}