blob: 10634866c64811ce1f451ba8d368ff082060362b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
Description: tcp_fragment fragmentation can exceed socket memory limits
References:
https://patchwork.ozlabs.org/patch/1117156/
https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-001.md
Notes:
Bugs:
upstream: released (5.2-rc6) [f070ef2ac66716357066b683fb0baf55f8191a2e]
4.19-upstream-stable: released (4.19.52) [ec83921899a571ad70d582934ee9e3e07f478848]
4.9-upstream-stable: released (4.9.182) [e358f4af19db46ca25cc9a8a78412b09ba98859d]
3.16-upstream-stable: released (3.16.69) [dc97a907bc76b71c08e7e99a5b1b30ef4d5e4a85]
sid: released (4.19.37-4) [bugfix/all/tcp-tcp_fragment-should-apply-sane-memory-limits.patch]
4.19-buster-security: N/A "Fixed before branching point"
4.9-stretch-security: released (4.9.168-1+deb9u3) [bugfix/all/tcp-tcp_fragment-should-apply-sane-memory-limits.patch]
3.16-jessie-security: released (3.16.68-2) [bugfix/all/tcp-tcp_fragment-should-apply-sane-memory-limits.patch]
|
