diff --git a/docs/reference/release-notes/8.15.0.asciidoc b/docs/reference/release-notes/8.15.0.asciidoc
index f1734482f5a37..e2314381a4b06 100644
--- a/docs/reference/release-notes/8.15.0.asciidoc
+++ b/docs/reference/release-notes/8.15.0.asciidoc
@@ -3,6 +3,25 @@
 
 Also see <<breaking-changes-8.15,Breaking changes in 8.15>>.
 
+
+[[known-issues-8.15.0]]
+[float]
+=== Known issues
+* The `pytorch_inference` process used to run Machine Learning models can consume large amounts of memory.
+In environments where the available memory is limited, the OS Out of Memory Killer will kill the `pytorch_inference`
+process to reclaim memory. This can cause inference requests to fail.
+Elasticsearch will automatically restart the `pytorch_inference` process
+after it is killed up to four times in 24 hours. (issue: {es-issue}110530[#110530])
+
+* Pipeline aggregations under `time_series` and `categorize_text` aggregations are never
+returned (issue: {es-issue}111679[#111679])
+
+* Elasticsearch will not start on Windows machines if
+[`bootstrap.memory_lock` is set to `true`](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration-memory.html#bootstrap-memory_lock).
+Either downgrade to an earlier version, upgrade to 8.15.1, or else follow the
+recommendation in the manual to entirely disable swap instead of using the
+memory lock feature (issue: {es-issue}111847[#111847])
+
 [[breaking-8.15.0]]
 [float]
 === Breaking changes
@@ -19,11 +38,6 @@ Rollup::
 Search::
 * Change `skip_unavailable` remote cluster setting default value to true {es-pull}105792[#105792]
 
-[[known-issues-8.15.0]]
-[float]
-=== Known issues
-* Elasticsearch will not start on Windows machines when the recommended [bootstrap.memory_lock: true](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration-memory.html#bootstrap-memory_lock) setting is configured due to [native access refactoring](https://github.com/elastic/elasticsearch/pull/111866). The workaround for 8.15.0 is to downgrade to the previous version.  This issue will be fixed in 8.15.1.
-
 [[bug-8.15.0]]
 [float]
 === Bug fixes