{"id":"CVE-2021-37692","aliases":["BIT-tensorflow-2021-37692","EUVD-2021-0418","GHSA-cmgw-8vpc-rc59","PYSEC-2021-314","PYSEC-2021-605","PYSEC-2021-803","openSUSE-SU-2022:10014-1","openSUSE-SU-2024:12116-1"],"status":"published","title":"Segfault on strings tensors with mistmatched dimensions in TensorFlow","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00172,"percentile":0.06671,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-20"],"published":"2021-08-12T23:00:14Z","modified":"2026-10-20T10:54:17Z","fixes":[{"ecosystem":"PyPI","package":"tensorflow","fixed_in":["2.5.1","2.3.4","2.4.3"],"sources":["ghsa","osv"]},{"ecosystem":"PyPI","package":"tensorflow-cpu","fixed_in":["2.5.1","2.3.4","2.4.3"],"sources":["ghsa","osv"]},{"ecosystem":"PyPI","package":"tensorflow-gpu","fixed_in":["2.5.1","2.3.4","2.4.3"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"tensorflow","fixed_in":["2.6.0"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"tensorflow","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0rc0"},{"fixed":"2.5.1"}]}]},{"source":"ghsa","ecosystem":"PyPI","package":"tensorflow-cpu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0rc0"},{"fixed":"2.5.1"}]}]},{"source":"ghsa","ecosystem":"PyPI","package":"tensorflow-gpu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0rc0"},{"fixed":"2.5.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"tensorflow","ranges":[{"type":"SEMVER","events":[{"introduced":"2.5.0"},{"fixed":"2.6.0"}]}]},{"source":"osv","ecosystem":"PyPI","package":"tensorflow","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0rc0"},{"fixed":"2.5.1"}]}],"versions":["2.5.0"]},{"source":"osv","ecosystem":"PyPI","package":"tensorflow-cpu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0rc0"},{"fixed":"2.5.1"}]}],"versions":["2.5.0"]},{"source":"osv","ecosystem":"PyPI","package":"tensorflow-gpu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0rc0"},{"fixed":"2.5.1"}]}],"versions":["2.5.0"]},{"source":"osv","ecosystem":"PyPI","package":"tensorflow","ranges":[{"type":"GIT","events":[{"introduced":"0"},{"fixed":"8721ba96e5760c229217b594f6d2ba332beedf22"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"},{"fixed":"2.3.4"},{"introduced":"2.4.0"},{"fixed":"2.4.3"}]}],"versions":["2.3.0","2.3.1","2.3.2","2.3.3","2.4.0","2.4.1","2.4.2"]},{"source":"osv","ecosystem":"PyPI","package":"tensorflow-cpu","ranges":[{"type":"GIT","events":[{"introduced":"0"},{"fixed":"8721ba96e5760c229217b594f6d2ba332beedf22"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"},{"fixed":"2.3.4"},{"introduced":"2.4.0"},{"fixed":"2.4.3"}]}],"versions":["2.3.0","2.3.1","2.3.2","2.3.3","2.4.0","2.4.1","2.4.2"]},{"source":"osv","ecosystem":"PyPI","package":"tensorflow-gpu","ranges":[{"type":"GIT","events":[{"introduced":"0"},{"fixed":"8721ba96e5760c229217b594f6d2ba332beedf22"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"},{"fixed":"2.3.4"},{"introduced":"2.4.0"},{"fixed":"2.4.3"}]}],"versions":["2.3.0","2.3.1","2.3.2","2.3.3","2.4.0","2.4.1","2.4.2"]},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP3","package":"bazel-skylib1.0.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.3-bp153.2.1"}]}],"bundled":63},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP3","package":"bazel3.7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.2-bp153.4.1"}]}],"bundled":63},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP3","package":"tensorflow2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP3","package":"tensorflow2-lite","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP3","package":"tensorflow2_2_6_0-gnu-hpc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP3","package":"tensorflow2_2_6_0-gnu-openmpi2-hpc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"bazel-skylib1.0.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.3-bp153.2.1"}]}],"bundled":63},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"bazel3.7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.2-bp153.4.1"}]}],"bundled":63},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"tensorflow2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"tensorflow2-lite","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"tensorflow2_2_6_0-gnu-hpc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"tensorflow2_2_6_0-gnu-openmpi2-hpc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.0-bp153.2.3.1"}]}],"bundled":63}],"products":[{"vendor":"google","product":"tensorflow"},{"vendor":"tensorflow","product":"tensorflow"}],"references":[{"url":"https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cmgw-8vpc-rc59","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/tensorflow/tensorflow/pull/50508","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-37692","tags":["web","advisory"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-605.yaml","tags":["web"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-803.yaml","tags":["web"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-314.yaml","tags":["web"]},{"url":"https://github.com/advisories/GHSA-cmgw-8vpc-rc59"},{"url":"https://github.com/tensorflow/tensorflow","tags":["package"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/U25ZU2T5T4LOLSIYIMGC5PLU4PQQMJE5/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1173128","tags":["report"]},{"url":"https://bugzilla.suse.com/1173314","tags":["report"]},{"url":"https://bugzilla.suse.com/1178287","tags":["report"]},{"url":"https://bugzilla.suse.com/1178564","tags":["report"]},{"url":"https://bugzilla.suse.com/1179455","tags":["report"]},{"url":"https://bugzilla.suse.com/1181864","tags":["report"]},{"url":"https://bugzilla.suse.com/1186860","tags":["report"]},{"url":"https://bugzilla.suse.com/1189423","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37638","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37692","tags":["web"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23595","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2021-37692","title":"Segfault on strings tensors with mistmatched dimensions in TensorFlow","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:00:14Z","modified":"2024-08-04T01:23:01.419Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T14:32:58.359368Z"}],"euvd":[{"id":"EUVD-2021-0418","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:00:14Z","modified":"2024-08-04T01:23:01Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T03:24:27.254804Z"}],"ghsa":[{"id":"GHSA-cmgw-8vpc-rc59","title":"Segfault on strings tensors with mistmatched dimensions, due to Go code","description":"### Impact\nUnder certain conditions, Go code can trigger a segfault in string deallocation.\n\n\nFor string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function.  However, tensor structure isn't checked until encoding to avoid a performance penalty.  The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions).\n\nTo fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written.\n\n### Patches\nWe have patched the issue in GitHub commit [8721ba96e5760c229217b594f6d2ba332beedf22](https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22) (merging [#50508](https://github.com/tensorflow/tensorflow/pull/50508)).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.                                                                                                                                               \n\n### For more information\nPlease consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.\n\n### Attribution\nThis vulnerability has been reported externally via a [fixing PR](https://github.com/tensorflow/tensorflow/pull/50508).","status":"published","published":"2021-08-25T14:38:57Z","modified":"2024-11-13T21:27:22Z","cvss":[{"version":"4.0","score":6.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T14:38:18.163845Z"}],"nvd":[{"id":"CVE-2021-37692","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:15:08.967Z","modified":"2026-06-17T04:00:59.76Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":2.1,"vector":"AV:L/AC:L/Au:N/C:N/I:N/A:P","level":"low","assessor":"primary"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T14:06:56.943671Z"}],"osv":[{"id":"CVE-2021-37692","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:15:08.967Z","modified":"2026-10-20T10:54:17.978643593Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:44:20.434873Z"},{"id":"GHSA-cmgw-8vpc-rc59","title":"Segfault on strings tensors with mistmatched dimensions, due to Go code","description":"### Impact\nUnder certain conditions, Go code can trigger a segfault in string deallocation.\n\n\nFor string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function.  However, tensor structure isn't checked until encoding to avoid a performance penalty.  The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions).\n\nTo fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written.\n\n### Patches\nWe have patched the issue in GitHub commit [8721ba96e5760c229217b594f6d2ba332beedf22](https://github.com/tensorflow/tensorflow/commit/8721ba96e5760c229217b594f6d2ba332beedf22) (merging [#50508](https://github.com/tensorflow/tensorflow/pull/50508)).\n\nThe fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.                                                                                                                                               \n\n### For more information\nPlease consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.\n\n### Attribution\nThis vulnerability has been reported externally via a [fixing PR](https://github.com/tensorflow/tensorflow/pull/50508).","status":"published","published":"2021-08-25T14:38:57Z","modified":"2026-07-08T06:28:58.551159598Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"},{"version":"4.0","score":6.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium"}],"cwes":["CWE-20"],"updated_at":"2026-11-02T15:46:45.28161Z"},{"id":"BIT-tensorflow-2021-37692","title":"Segfault on strings tensors with mistmatched dimensions in TensorFlow","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2024-03-06T11:16:40.37Z","modified":"2026-09-08T08:48:16.738122919Z","updated_at":"2026-11-02T15:28:35.51001Z"},{"id":"openSUSE-SU-2022:10014-1","title":"Security update for tensorflow2","description":"\nThis update for tensorflow fixes the following issues:\n\n\nUpdate to TF2 2.6.0 which fixes multiple CVEs (boo#1189423).\n\n- Introduction of bazel6.3 and basel-skylib1.0.3 as build\n  dependencies.\n  The latter has been adapted to all a version in its package\n  name (if %set_ver_suffix is set to 1). This allows multiple\n  versions to exist for one product (not installed).\n  NOTE: basel-skylib1.0.3 does not exist in oS:Factory:\n  basel-skylib in oS:Factory - the base version - is 1.0.3.\n","status":"published","published":"2022-06-18T16:01:26Z","modified":"2026-02-04T02:20:34.480131Z","updated_at":"2026-11-02T16:58:32.653274Z"},{"id":"openSUSE-SU-2024:12116-1","title":"tensorflow-lite-2.9.1-1.1 on GA media","description":"These are all security issues fixed in the tensorflow-lite-2.9.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:04:19.609756Z","updated_at":"2026-11-02T16:58:35.485255Z"},{"id":"PYSEC-2021-314","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:15:00Z","modified":"2023-12-06T01:01:24.71787Z","updated_at":"2026-11-02T15:52:52.682031Z"},{"id":"PYSEC-2021-605","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:15:00Z","modified":"2023-12-06T01:01:24.71787Z","updated_at":"2026-11-02T15:52:53.119977Z"},{"id":"PYSEC-2021-803","description":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.","status":"published","published":"2021-08-12T23:15:00Z","modified":"2023-12-06T01:01:24.71787Z","updated_at":"2026-11-02T15:52:53.119977Z"}]}}