I received this question several times in the last couple of days via email, post comments and support cases – so I decided to answer it here for your benefit.
I tried to answer this question in my SharePoint patching demystified article but it seems it is still not clear.
This is the page I'm talking about:
As shown on the screenshot the version number is the Configuration database version – it is not a "farm patch level". Something like a farm patch level does not exist as SharePoint patching is pretty complex and actually means to patch various different components.
The answer why the above listed version number did not change is simple: The configuration database schema is not changed in October CU. Neither in SharePoint 2010, nor in SharePoint 2013. For SharePoint 2010 that can easily be explained: The only component directly accessing the configuration database is the SharePoint foundation component – which is more or less the database access layer for SharePoint Server. In October 2014 CU for SharePoint 2010 we did not release any patches for SharePoint Foundation – so the configuration database version cannot change.
What is the learning from this? Don't use the Configuration database version number to verify the patch level of your farm.
More details here: SharePoint patching demystified