Nope, it's not inherited, it just kinda-sorta acts like it in some cases.

Author: tabatkins

css-scroll-anchoring/Overview.bs

@@ -228,32 +228,36 @@ or exclude portions of the DOM from the anchor node selection algorithm.
 Name: overflow-anchor
 Value: auto | none
 Initial: auto
-Inherited: yes
+Inherited: no
 </pre>
 
 Values are defined as follows:
 
 <dl dfn-type=value dfn-for=overflow-anchor>
 	: <dfn>auto</dfn>
 	::
-		Declares that the DOM subtree rooted at the element
-		is eligible to participate in the <a>anchor node selection algorithm</a>
+		Declares that the element
+		is potentially eligible to participate in the <a>anchor node selection algorithm</a>
 		for any scrolling box created by the element or an ancestor.
+
 	: <dfn>none</dfn>
 	::
-		Declares that the DOM subtree rooted at E
-		is <em>not</em> eligible to participate in the <a>anchor node selection algorithm</a>
+		Declares that the element and its descendants
+		(that aren't nested inside of another scrolling element)
+		are <em>not</em> eligible to participate in the <a>anchor node selection algorithm</a>
 		for any scrolling box created by the element or an ancestor.
 </dl>
 
+Note: It is not possible to turn scroll anchoring "back on"
+for descendants of a ''scroll-anchoring: none'' element.
+However, descendant <a>scroll containers</a> automatically "turn it back on"
+(for their own scrolling box)
+unless they explicitly have ''scroll-anchoring: none'' set on them as well.
+
 Note: The <code>overflow-anchor</code> property was also proposed (with different values)
 for <a href="http://tabatkins.github.io/specs/css-sticky-scrollbars/">CSS Sticky Scrollbars</a>,
 which has now been <a href="https://tabatkins.github.io/specs/css-sticky-scrollbars/#intro">superseded</a>.
 
-Issue: The spec originally said that 'overflow-anchor' isn't inherited,
-but, uh, I don't know how that works,
-given that the values are defined as affecting their descendants.
-
 <h2 id='priv-sec'>
 Privacy and Security Considerations</h2>